On 2014-02-09 09:38, Axel Röber wrote:
Hi, a few days ago I switched the Hibernate version from 4.2.7 (JPA2) to 4.3.1 (JPA2.1) on an existing (spring) application. Everthing seems to work fine but I was wondering why the application slows down. Then I detected a very big H2 trace file (.trace.db) only containing 'The object is already closed' org.h2.jdbc.JdbcSQLExceptions. It seems that nearly every Update and Insert statement throws this exception. Going back to Hibernate 4.2 and the exceptions are thrown no longer. This can be seen by using H2 Version 1.3.175 and Version 1.3.174 (in embedded mode). Any ideas on this? How can I change the Hibernate, Spring and/or H2 configuration to avoid this?
That looks like a bug in Hibernate - it should not be calling that method on a closed Statement object. I suggest you bring it up on the Hibernate mailing list. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
