-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Throw an exception when trying to read from a broken connection #1923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
gkorland
merged 2 commits into
redis:master
from
mina-asham:do-not-read-from-broken-connection
Mar 26, 2019
Merged
Throw an exception when trying to read from a broken connection #1923
gkorland
merged 2 commits into
redis:master
from
mina-asham:do-not-read-from-broken-connection
Mar 26, 2019
Conversation
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
Contributor
mina-asham
commented
Jan 5, 2019
- When attempting to read from a broken connection, Jedis could potentially try to read some corrupt data and interpret it according to the Redis protocol, this makes it throw an exception instead of trying that.
- Jedis causes OutOfMemoryException after SocketTimeoutException #1747 describes that possible misinterpretations of the protocol can lead to trying to create very large arrays
- Also refactor clientPause test, it was testing that clients fail, CLIENT PAUSE command pauses all clients, so they should be expected to be delayed rather than failed
- When attempting to read from a broken connection, Jedis could potentially try to read some corrupt data and interpret it according to the Redis protocol, this makes it throw an exception instead of trying that. - redis#1747 describes that possible misinterpretations of the protocol can lead to trying to create very large arrays - Also refactor clientPause test, it was testing that clients fail, CLIENT PAUSE command pauses all clients, so they should be expected to be delayed rather than failed
sazzad16
approved these changes
Jan 5, 2019
Contributor
sazzad16
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Contributor
Contributor
Author
|
ping, it's quite a small diff... |
Contributor
Author
|
Another ping... @marcosnils @gkorland |
Contributor
|
LGTM. @smadasu I've changed it to 3.0.2 as it's not adding anything new features. |
Contributor
|
@marcosnils Sure! |
|
what does it mean broken connection, what are the possibilities to broke a connection |
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.