Hi,

Since upgrading from Hibernate 3.1.3 to 3.2.5, I'm receiving exceptions in persistence of fields that map to identity columns:

... snip ...



This exception only occurs in the following situation:


1. Transaction opened

2. Class is opened via Hibernate:


3. Entry is added to a mapped list in the class

4. Class is saved via Hibernate:



5. Exception occurs in persistence of entry added in step 3.

Note that this exception doesn't occur when the class is saved as part of a separate transaction from opening.

Looking at the Javadocs for DelayedPostInsertIdentifier, it appears that this should only be present when classes are being persisted outside of a transaction so am unsure why this is happening in this - and only this - situation.

Transaction management in the application is being handled by Spring's TransactionProxyFactoryBean and all methods are set to PROPAGATION_REQUIRED.

We're using JBoss's JTA transaction manager but we are only using JBoss 4.0.1 - is this still supported by Hibernate 3.2?

Problem solved.

Did some digging in the Hibernate code - it appears that even though the Spring JTATransactionManager was initialised by the application, Hibernate was falling back to using JDBCTransactionManager because we hadn't explicitly set the transaction manager for Hibernate.

Hibernate's call to see whether it's participating in a transaction was therefore calling the wrong transaction manager, which is returning false.

It does seem odd that from Hibernate 3.1.x to Hibernate 3.2 that the existing JTA transaction manager isn't being picked up - perhaps this should be documented somewhere (if it isn't already?)...

For anyone else in a similar situation, the problem was resolved by setting the jtaTransactionManager property below to reference the application's JTA transaction manager: