Skip to content

Throw ServiceUnavailableException when socket write fails #312

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
merged 3 commits into from
Feb 6, 2017

Conversation

lutovich
Copy link
Contributor

Previously ClientException was thrown which was incorrect and resulted in connections not being properly disposed.

Also made small cleanup of unused/test-only methods and classes.

@zhenlineo
Copy link
Contributor

Could you add test for encrypted connections too?

Previously `ClientException` was thrown which was incorrect and resulted in
connections not being properly disposed.
@lutovich lutovich force-pushed the 1.1-better-exception branch from f85d046 to b46f48a Compare February 6, 2017 10:54
@lutovich
Copy link
Contributor Author

lutovich commented Feb 6, 2017

@zhenlineo changed test in CausalClusteringIT uses encrypted channel with basic auth. Also rebased this PR.

@zhenlineo zhenlineo merged commit cd90440 into neo4j:1.1 Feb 6, 2017
@lutovich lutovich deleted the 1.1-better-exception branch February 9, 2017 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants