Skip to content

Conversation

@zhenlineo
Copy link
Contributor

that is caused by forgetting to flip a buffer back after connection error.
Close the socket channel directly if server already mark the end of the channel

…nnection error

Close the socket channel directly if server already mark the end of the channel
@lutovich
Copy link
Contributor

@zhenlineo it would be really nice to have tests for flipping the buffer on connection error and logs for empty best effort catch blocks.

@zhenlineo
Copy link
Contributor Author

zhenlineo commented Oct 13, 2016

@lutovich Logging for this specific best effort channel.close error is not very helpful. As this is not the real error. The error that the driver cannot read/write more data from the channel is the real error that a user should worry about. Whether I close this socket connection correctly or the socket just crashed is not really important as next session, they will get another new connection.

@zhenlineo zhenlineo closed this Oct 13, 2016
@zhenlineo zhenlineo reopened this Oct 13, 2016
@zhenlineo
Copy link
Contributor Author

@lutovich Be free to find me if you still disagree. I merge this now as it is an important bug fix.

@zhenlineo zhenlineo merged commit 68e6344 into neo4j:1.0 Oct 14, 2016
@zhenlineo zhenlineo deleted the 1.0-buffer-flip branch October 14, 2016 08:57
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