This particular issue came up when testing a Spring Boot application but I eventually tracked it down to the use of OpenEntityManagerInViewInterceptor. It's very hard to replicate and I'm not totally sure if the issue is with Spring, WildFly or a combination of both.
I'll attach an issue project which will explain more.
Affects: 4.1 RC2
Issue Links:
#13599 readOnly transaction doesn't work with JPA and Hibernate 4
This has been addressed through revised Connection reset logic, never kicking in for JTA transactions now. Apparently an accidental Connection.setReadOnly(false) call, despite that being the default state of a JDBC Connection, can cause side effects in a JTA scenario...
More importantly for the general case, this change also avoids Connection retrieval just for reset purposes.
Phil Webb opened SPR-12118 and commented
This particular issue came up when testing a Spring Boot application but I eventually tracked it down to the use of
OpenEntityManagerInViewInterceptor
. It's very hard to replicate and I'm not totally sure if the issue is with Spring, WildFly or a combination of both.I'll attach an issue project which will explain more.
Affects: 4.1 RC2
Issue Links:
Referenced from: commits spring-projects/spring-boot@6ee18fb
The text was updated successfully, but these errors were encountered: