Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InvocationFuture async calls don't detect lost operations #6250

Closed
pveentjer opened this issue Sep 18, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@pveentjer
Copy link
Member

commented Sep 18, 2015

A sync call (future.get) will call is still running and if returns false, then timeout.

But future using an andThen won't trigger this behavior. So if a future is only used this way and the operation/response got lost, it won't be detected.

@pveentjer pveentjer added this to the 3.6 milestone Sep 18, 2015

metanet added a commit to metanet/hazelcast that referenced this issue Sep 21, 2015

Timeout original operation when no response is received for IsStillEx…
…ecutingOperation

The problem is as follows: IsStillExecutingOperation is used to timeout a remove invocation by InvocationRegistry or either making the call sync by calling .get() on the future reference. If no response is received for the IsStillExecutingOperation invocation, then the original invocation does not times out.

Fixes hazelcast#6250

metanet added a commit to metanet/hazelcast that referenced this issue Sep 21, 2015

Timeout original operation when no response is received for IsStillEx…
…ecutingOperation

The problem is as follows: IsStillExecutingOperation is used to timeout a remote invocation by InvocationRegistry or either making the call sync by calling .get() on the future reference. If no response is received for the IsStillExecutingOperation invocation, then the original invocation does not times out.

Fixes hazelcast#6250

tombujok added a commit to tombujok/hazelcast that referenced this issue Oct 14, 2015

Timeout original operation when no response is received for IsStillEx…
…ecutingOperation

The problem is as follows: IsStillExecutingOperation is used to timeout a remote invocation by InvocationRegistry or either making the call sync by calling .get() on the future reference. If no response is received for the IsStillExecutingOperation invocation, then the original invocation does not times out.

Fixes hazelcast#6250

@pveentjer pveentjer modified the milestones: 3.7, 3.6 Nov 4, 2015

@pveentjer pveentjer self-assigned this Nov 4, 2015

@pveentjer pveentjer reopened this Dec 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.