Closing BerkeleyDB resources, make handling TcpClient channels failings and disconnects identical #37
Conversation
This file contains 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
pron
added a commit
that referenced
this pull request
Aug 26, 2015
Closing BerkeleyDB resources, make handling TcpClient channels failings and disconnects identical
|
Cool. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
prior to this changes any error in TcpClient channel leads to setting Component in an unavailable state no matter what channel fails. That was not totally correct cause we have to check only the main channel (co.paralleluniverse.galaxy.netty.AbstractTcpClient#channel) when calling setReady(false) on this component.