Skip to content
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

arangodb-java-driver-384 "java.net.SocketException: Socket closed" #385

Conversation

wajda
Copy link
Contributor

@wajda wajda commented Apr 20, 2021

fixes #384

Before returning a connection instance to the caller of the connect() method, check if the connection obtained from the host handler is still alive (i.e. is the associated socket is open), otherwise discard it and get a new one until a usable connection is found.

@rashtao rashtao self-assigned this Apr 21, 2021
@wajda wajda force-pushed the bugfix/arangodb-java-driver-384-socket-closed-in-cluster-mode branch from 850415e to fdfa78d Compare April 21, 2021 14:53
@wajda
Copy link
Contributor Author

wajda commented Apr 27, 2021

Hi Michele,
Did you have a chance to take a look at the PR?
This issue holds our project release. I wonder if I should wait for the fixed upstream version, or should I proceed with a fork?

@rashtao rashtao self-requested a review April 29, 2021 12:36
@rashtao rashtao merged commit 67a5409 into arangodb:master Apr 29, 2021
@wajda wajda deleted the bugfix/arangodb-java-driver-384-socket-closed-in-cluster-mode branch May 7, 2021 13:52
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.

"java.net.SocketException: Socket closed" when in a cluster mode + Docker + acquireHostList enabled
2 participants