Handle unknown runtime exception while reading entries#2993
Merged
Conversation
merlimat
reviewed
Nov 15, 2018
Contributor
|
The suspicion is that this might be due to the scenario described in netty/netty#8563 |
massakam
approved these changes
Nov 16, 2018
merlimat
pushed a commit
that referenced
this pull request
Dec 13, 2018
* Handle unknown runtime exception while reading entries * make asyncReadEntry0 private
2 tasks
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
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.
Motivation
Recently we have seen below runtime-exception while reading entries at broker and broker is not handling it correctly and not completing read callback so, dispatch get stuck for the subscription.
Modifications
Handle NPE and complete the callback with failure.
Result
Dispatch will not be blocked if there is runtime exception while reading entries.