Re: [wildfly-dev] (transaction enlistment for ACID but none for BASE...) update on WildFly NoSQL prototype integration...

The NoSQL prototype now has transaction enlistment for Neo4j (one phase wrapper). Test example link [1] shows a CMT test bean method and [2] shows a BMT test bean method. Currently, in a JTA transaction the Neo4j Session survives ending the JTA transaction. It might be better to close the Neo4j Session when the JTA transaction ends, which would require the application to get a new Session, this would ensure that applications don't forget to close the session, with the down side that with BMT, application code would need to call the Neo4j Driver.session(), to get a new Session instance after each JTA transaction ends. After a session is closed, there is no guarantee that another session can be obtained, as the next Driver.session() may time out if the internal pool of Driver sessions, is empty and the configured time limit (neo4j.driver.acquireSessionTimeout) is exceeded (defaults to 30 seconds). So, there are costs to automatically closing Neo4j Sessions at JTA transaction end time. Although, you could say that closing the Session, after each transaction, gives other threads a change to use the Session that isn't really closed, but instead is really returned to the internal Driver sessions pool. By the way, the Neo4j Session class, is what applications use to access the database. Thanks, Scott [1] https://github.com/scottmarlow/wildfly/blob/nosql-dev9/testsuite/nosql/sr... [2] https://github.com/scottmarlow/wildfly/blob/nosql-dev9/testsuite/nosql/sr... On 06/29/2016 09:50 AM, Scott Marlow wrote: