Check error stream is not null before notifying error #961
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.
Fixes #955
We are getting this exception frequently, when the network to the server is poor (ie., there are a lot of dropped packets at the server, for example):
I can't really see how the
err
variable inSessionChannel
can be null, but apparently sometimes it is.This kind of check is already done in
AbstractChannel.notifyError
(although only for theout
stream), so I'm doing it inSessionChannel
as well.