Handle IOException and SocketException#14
Merged
HTHou merged 5 commits intoapache:mainfrom Aug 28, 2024
Merged
Conversation
CritasWang
approved these changes
Aug 28, 2024
Contributor
CritasWang
left a comment
There was a problem hiding this comment.
Cool, Now the client has become stronger～
LGTM
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
3 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.
This PR fixes #13
SocketExceptionis caused by the unhandled Exception inOpenmethod, stemming from the initialization process ofTCPClient.IOExceptionoccurred due to a missing transport closure in theReconnectmethod when only one single endpoint is available.With these changes, a unified exception type is now returned when a query statement execution fails.