InvocationFuture async calls don't detect lost operations #6250

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

Projects

None yet

1 participant

@pveentjer
Member

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 metanet added a commit to metanet/hazelcast that referenced this issue Sep 21, 2015
@metanet metanet 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 #6250
afb94b8
@metanet metanet added a commit to metanet/hazelcast that referenced this issue Sep 21, 2015
@metanet metanet 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 #6250
2fda0e4
@metanet metanet closed this in #6269 Sep 21, 2015
@tombujok tombujok added a commit to tombujok/hazelcast that referenced this issue Oct 14, 2015
@metanet @tombujok metanet + tombujok 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 #6250
635733a
@pveentjer pveentjer modified the milestone: 3.7, 3.6 Nov 4, 2015
@pveentjer pveentjer self-assigned this Nov 4, 2015
@pveentjer pveentjer reopened this Dec 28, 2015
@devOpsHazelcast devOpsHazelcast pushed a commit that closed this issue Jan 15, 2016
@metanet metanet 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 #6250
a5d62e5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment