Hi

We are currently using Hibernate 3.3.1 + Oracle 10G + Spring 2.5 for dependency injection, transactions etc

We have run into a number of occasions recently where hibernate thinks there has been a commit (ie the code has run its course with no exceptions which should have resulted in a commit) however this has not resulted in actual rows committed to the database.

Turning up the logging level shows hibernate issuing insert and update statements to the database.

Is it possible under normal cirumstances that hibernate may not know that a rollback has taken place?

Are there settings to make hibernate look more closely at whether a transaction has passed or not?

Thanks

Are your classes annotated with @Transactional?

I just had the opposite effect, loaded collection in one class, passed it to another but some context information got lost.
Log showed commit of transaction when the collection was passed from one class to another.
After adding @Transactional the commit went away

Hi

Thanks for reply...

Sometimes we use the transaction annotation and sometimes we use manual transactions.

In both cases we get rollbacks that cannot be explained and which do not cause any form of exception in the Java code.