Adding workaround for the case when a connect gets stuck forever #1
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.
I hope to fix twitter-archive#117 with this pull request.
I was never able to reproduce the issue in our test environment. In the end I put my change on some of the production servers and I could verify via behavior and logging that it actually fixed my problem.
This is a workaround and I guess the problem is somewhere inside netty. But since there is already a branch to move to netty 4, I don't think it is worth to track down the bug there.
PS: Currently bugs can not be reported to this project.