I am trying to persist a new class that contains some associations. The save is wrapped in a transaction using the Spring Framework HibernateTransactionManager. However the problem I'm having seems to be with hibernate.

When I try to persist the new class the first action in the queue is flushed as normal. When the next object which is an association of the first class that was persisted is flushed there is an exception and so hibernate rollbacks as it should. However the first object inserted in the transaction is not rolled back, it is persisted in the database. It looks like there is some its auto committing going on but I thought hibernate turned off auto commit at the start of a transaction. Anyone have any ideas?


Btw I am using c3p0 for database pooling on a oracle database.

Thanks,
T.J

NO - this is a common misconception. Please look at the JavaDoc related to FlushMode. The semantics you want are probably to set FlushMode.COMMIT on your session upon retrieval of the session. I don't remember the API of spring well enough, but this is probably something you can set up when you're setting up the HibernateTransactionManager bean.

Thanks for your response.

This is probably a very basic question but shouldnt a session last for the entire duration of a transaction and all connections used in that session have auto commit turned off. The session is then committed at the end of the transaction so any exception before the commit is rolled back properly. Is my understanding of transactions wrong?