Ensure compatibility with Hibernate 4.2 [SPR-10255]

[spring-projects-issues]

Juergen Hoeller opened SPR-10255 and commented

Hibernate 4.2 RC1 got released a few days ago. Their GA can be expected in time for our 3.2.2 release, so let's make sure that everything keeps working fine there, both with our orm.hibernate4 package and with our JPA vendor support.

---

Issue Links:

• Support for Hibernate ORM 5.0 [SPR-11694] #16316 Support for Hibernate ORM 5.0

0 votes, 5 watchers

[spring-projects-issues]

Juergen Hoeller commented

OK, let's consider this as compatible then, just quickly retesting against Hibernate 4.2 GA once it becomes available.

Juergen

[spring-projects-issues]

Andreas Joseph Krogh commented

When using Spring's JdbcTemplate inside a transactional-service with the JpaTransactionmanager and the HibernateJpaDialect an exception is thrown.

Using Hibernate-4.2.0.Final, JPA, Spring-3.2.2 and I get:

Caused by: java.sql.SQLException: PooledConnection has already been closed.
        at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:86)
        at com.sun.proxy.$Proxy19.commit(Unknown Source)
        at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:112)
        ... 44 more

This happens both with c3p0 and tomcat-pool that comes with tomcat7.

I've tested in two projects with the same results. This doesn't happen with Hibernate-4.1.x

I know i should provide a test-case but I only have a scala-project at hand and you probably want that out of the equation...

[spring-projects-issues]

Phil Webb commented

Hi Andreas,

Thanks for raising this. I have opened #15028 to track this as a bug that we can target for 3.2.3.