-
Notifications
You must be signed in to change notification settings - Fork 22
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
Issue 148: "Stuck client" may not be detected in case of non-open socket #164
Conversation
@@ -601,7 +601,7 @@ public void replyReceived(Message originalMessage, Message message, Throwable er | |||
|
|||
void processIdleConnection() { | |||
Channel _channel = channel; | |||
if (_channel != null && _channel.isValid()) { | |||
if (_channel != null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is actually the fix !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@@ -601,7 +601,7 @@ public void replyReceived(Message originalMessage, Message message, Throwable er | |||
|
|||
void processIdleConnection() { | |||
Channel _channel = channel; | |||
if (_channel != null && _channel.isValid()) { | |||
if (_channel != null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
In case of unhandled exception on the server side we are marking the connection as "not valid" and thus we are not processing pending messages anymore.
With this change the processing of pending messages is executed even in case of "failed" NettyChannel.
The new test case hangs without this change
Fixes #164