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

Once socket enters exceptional state via SNDHWM or RCVHWM and nonblocking is used #113

Closed
ljackson opened this issue Nov 19, 2013 · 3 comments

Comments

@ljackson
Copy link

version 0.3.1

The socket will never be able to come out of the exceptional state as the recv and send methods continue to return exceptional state e.g. null.

I have some new code I am about to opensource that uses the NIO selectablechannel and I found that the default HWM of 1000 under large load can cause the socket to get into the exceptional state and never come out. If I get around to it I will add a unit test to reproduce.

@miniway
Copy link
Member

miniway commented Dec 6, 2013

Thanks for the comment, I'm waiting the test case.

@daveyarwood
Copy link
Contributor

@ljackson Do you have any additional information about this issue? There is not enough information here to investigate or take action.

@daveyarwood
Copy link
Contributor

Closing this issue, as there has been no further conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants