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

Client Interruption handling #7963

Closed
pveentjer opened this issue Apr 18, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@pveentjer
Copy link
Member

commented Apr 18, 2016

Unlike the serverside InvocationFuture, the ClientInvocationFuture will immediately propagate the InterruptedException if the calling thread gets interrupted. This can be a problem with both caller and callee need to agree on the fact that the operation did or did not get executed.

e.g. a lock acquire operation where the caller is interrupted and therefor the caller believes that the lock wasn't acquired, but actually on the serverside the lock is acquired since on the server there is no knowledge regarding the client interrupt status.

@pveentjer pveentjer added this to the 3.7 milestone Apr 18, 2016

@sancar sancar added the Team: Client label Apr 18, 2016

@pveentjer

This comment has been minimized.

Copy link
Member Author

commented May 6, 2016

I'm going to close ticket since it is a duplicate of:

#3978

@pveentjer pveentjer closed this May 6, 2016

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.