This repository was archived by the owner on Dec 24, 2022. It is now read-only.
socket is not set to null during transaction, after redis server stops, ...< 8000 /span>#195
Merged
mythz merged 1 commit intoServiceStack:v3from Mar 22, 2014
Merged
socket is not set to null during transaction, after redis server stops, ...#195mythz merged 1 commit intoServiceStack:v3from
mythz merged 1 commit intoServiceStack:v3from
Conversation
…s, then starts. after redis server stops, the sockets which are used by RedisClient in the transaction are not set to null. when the redis server is back on, socket exceptions will be thrown. move the try /catch logic into FlushSendBuffer instead.
mythz
added a commit
that referenced
this pull request
Mar 22, 2014
socket is not set to null during transaction, after redis server stops, ...
Member
|
change seems ok, thx. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
...then starts.
after redis server stops, the sockets which are used by RedisClient in
the transaction are not set to null. when the redis server is back on,
socket exceptions will be thrown. move the try /catch logic into
FlushSendBuffer instead.