amadfida opened a new issue, #14551: URL: https://github.com/apache/grails-core/issues/14551
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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
