You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When OptimisticLockingException are thrown during session.flush() as part of doCommit(), it has been observed that those transactions are not rolled back and are left open and Neo4j server keep those transaction alive, and keeping any locks on objects as well. There so no default transaction timeout in Neo4j, hence resulting in complete lock till restart.
The text was updated successfully, but these errors were encountered:
amadfida
changed the title
TX resulting OptimisticLockingExcepetion are never committed nor rolled back
Transactions resulting in OptimisticLockingExcepetion are never committed nor rolled back
Aug 30, 2018
When OptimisticLockingException are thrown during session.flush() as part of doCommit(), it has been observed that those transactions are not rolled back and are left open and Neo4j server keep those transaction alive, and keeping any locks on objects as well. There so no default transaction timeout in Neo4j, hence resulting in complete lock till restart.
https://github.com/spring-projects/spring-framework/blob/master/spring-tx/src/main/java/org/springframework/transaction/support/AbstractPlatformTransactionManager.java#L128 seems that we should set that to true in Neo4jDatastoreTransactionManager to handle roll backs during commit failures.
The text was updated successfully, but these errors were encountered: