Skip to content

Treat request errors as fatal #419

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 1 commit into from
Oct 17, 2017
Merged

Conversation

lutovich
Copy link
Contributor

@lutovich lutovich commented Oct 16, 2017

Fatal errors result in network channel being closed. Previously only some errors that originate in the driver were treated as fatal. However some errors received from the database mean communication is broken.

This PR makes protocol errors that start with Neo.ClientError.Request be treated as fatal. No ACK_FAILURE will be send for such errors and netty channel will be closed.

@lutovich lutovich requested a review from zhenlineo October 16, 2017 09:49
@lutovich lutovich force-pushed the 1.5-fatal-errors-from-db branch 3 times, most recently from 9f1e537 to 2168c2f Compare October 17, 2017 09:00
Fatal errors result in network channel being closed. Previously only
some errors that originate in the driver were treated as fatal.
However some errors received from the database mean communication
is broken.

This commit makes protocol errors that start with
`Neo.ClientError.Request` be treated as fatal. No ACK_FAILURE will be
send for such errors and netty channel will be closed.
@lutovich lutovich force-pushed the 1.5-fatal-errors-from-db branch from 2168c2f to 2124cac Compare October 17, 2017 09:16
@lutovich lutovich merged commit eb67a9c into neo4j:1.5 Oct 17, 2017
@lutovich lutovich deleted the 1.5-fatal-errors-from-db branch October 17, 2017 21:26
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.

1 participant