Specifically there is 1 tests that fails in both configurations for a total of 2 failures. The test class is org.hibernate.envers.test.integration.jta.JtaTransaction. The failure says:
JdbcServicesImpl.java:110 is a simple attempt to use the java.sql.Connection returned by the configured org.hibernate.service.jdbc.connections.spi.ConnectionProvider:
I don't think this is a problem with JBossTS.
I debugged into H2 JDBC and I can see that autocommit is true and that the insert is committed immediately.
I see that Ejb3Configuration.prepareProperties() sets autocommit to true. Maybe this value is finding its way into the connection.
This never failed prior to the move to JBossTS. Granted that does not unequivocally means JBossTS is at fault, but its smoke and where there is smoke there is a high likelihood there will be fire.
The auto-commit variable in Hibernate is consumed by the ConnectionProvider. Now it is possible that H2 is not being made properly aware that it is a data source. I am not completely familiar enough with that test to know what ConnectionProvider it uses etc.
This was fixed by adding ";AUTOCOMMIT=OFF" to the URL registered with the datasource.
This change caused failures in JtaTransaction. Those failures will be dealt with by HHH-6624.
Great to hear that; and the solution, as always, was pretty simple
Not so good though that this caused other test failures, but maybe they will be easier to track down.
Thanks a lot for taking care of this!
Bulk closing tickets resolved in released versions