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

[WFCORE-112] Long server shut-dow with unresponsive client with opened JNDI Context #24

Merged
merged 1 commit into from Oct 3, 2014

Conversation

elguardian
Copy link
Contributor

This removes the deadlock that is happening due to a network failure during closeAsync call.
The close async was doing this:

  1. send close (endpoint A)
  2. receive close (endpoint B)
  3. send close (endpoint B)
  4. receive close (endpoint A) -> close the channel
    If the network fails point 2 never takes place, then endpoint A waits
    forever. It is changed to:
  5. send close (endpoint A) -> close the channel
  6. receive close (endpoint B) -> close the channel

to a network failure during closeAsync call.
The close async was doing this: 
1) send close (endpoint A)
2) receive close (endpoint B)
3) send close (endpoint B) 
4) receive close (endpoint A) -> close the channel
If the network fails point 2 never takes place, then endpoint A waits
forever. It is changed to:
1) send close (endpoint A) -> close the channel
2) receive close (endpoint B) -> close the channel
dmlloyd added a commit that referenced this pull request Oct 3, 2014
[WFCORE-112] Long server shut-dow with unresponsive client with opened JNDI Context
@dmlloyd dmlloyd merged commit 6810b1b into jboss-remoting:master Oct 3, 2014
@elguardian elguardian deleted the WFCORE-112 branch October 3, 2014 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants