-
Notifications
You must be signed in to change notification settings - Fork 4k
netty: Fix receipt of ClosedChannelException instead of actual error.… #2255
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -99,6 +99,8 @@ class NettyClientTransport implements ConnectionClientTransport { | |
|
|
||
| @Override | ||
| public void ping(final PingCallback callback, final Executor executor) { | ||
| // The promise and listener always succeed in NettyClientHandler. So this listener handles the | ||
| // error case, when the channel is closed and the NettyClientHandler no longer in the pipeline. | ||
| ChannelFutureListener failureListener = new ChannelFutureListener() { | ||
| @Override | ||
| public void operationComplete(ChannelFuture future) throws Exception { | ||
|
|
@@ -234,17 +236,17 @@ public Attributes getAttrs() { | |
| * Convert ChannelFuture.cause() to a Status, taking into account that all handlers are removed | ||
| * from the pipeline when the channel is closed. Since handlers are removed, you may get an | ||
| * unhelpful exception like ClosedChannelException. | ||
| * | ||
| * <p>This method must only be called on the event loop. | ||
| */ | ||
| private Status statusFromFailedFuture(ChannelFuture f) { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Add a comment that this may only be called on the event loop. |
||
| Throwable t = f.cause(); | ||
| if (t instanceof ClosedChannelException) { | ||
| synchronized (this) { | ||
| Status shutdownStatus = lifecycleManager.getShutdownStatus(); | ||
| if (shutdownStatus == null) { | ||
| return Status.UNKNOWN.withDescription("Channel closed but for unknown reason"); | ||
| } | ||
| return shutdownStatus; | ||
| Status shutdownStatus = lifecycleManager.getShutdownStatus(); | ||
| if (shutdownStatus == null) { | ||
| return Status.UNKNOWN.withDescription("Channel closed but for unknown reason"); | ||
| } | ||
| return shutdownStatus; | ||
| } | ||
| return Utils.statusFromThrowable(t); | ||
| } | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What if getShutdownThrowable() is 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.
Then null is propagated to the
PingCallback. The API spec seems to allow it. If our code works correctly, we should never get aClosedChannelExceptionwithout theClientTransportLifeCycleManagerknowing about it, no?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.
I don't believe PingCallback was intended to allow a null cause. And such a null cause is very difficult to debug.
We should just create a status in that case, like done elsewhere, maybe with the message "Ping failed but for unknown reason".