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

Fix Transaction#isOpen() after errors #375

Merged
merged 1 commit into from
May 19, 2017

Conversation

lutovich
Copy link
Contributor

ExplicitTransaction has a FAILED state which is reached when fatal connection error happens or Session#reset() is called. In both cases corresponding transaction on server will be rolled back by the database. This PR makes sure FAILED state is changed to ROLLED_BACK when transaction is closed. It's needed to make sure Transaction#isOpen() does not report status incorrectly after closing of a FAILED transaction.

`ExplicitTransaction` has a FAILED state which is reached when fatal
connection error happens or `Session#reset()` is called. In both
cases corresponding transaction on server will be rolled back by the
database. This commit makes sure FAILED state is changed to ROLLED_BACK
when transaction is closed. It's needed to make sure
`Transaction#isOpen()` does not report status incorrectly after
closing of a FAILED transaction.
@zhenlineo
Copy link
Contributor

LG, pls merge and forward merge

@lutovich lutovich merged commit 30cc1a4 into neo4j:1.1 May 19, 2017
@lutovich lutovich deleted the 1.1-tx-isOpen-reset branch May 19, 2017 10:15
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