Ignore unrecoverable ClosedChannelException errors #7246
Merged
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
graemerocher
requested review from
yawkat and
jameskleeh
and removed request for
yawkat
|
Kudos, SonarCloud Quality Gate passed! |
jameskleeh
approved these changes
Apr 27, 2022
yawkat
approved these changes
Apr 27, 2022
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.
Spurious log entries exist when an HTTP/2 browser drops the connection as a ClosedChannelException exception is thrown and propagated down the pipeline. Since it is not possible to recover from these exceptions this change just alters the behavior to swallow them the same as connection reset IO exceptions.
Fixes #7244