Hi folk,

we have a very strange problem in our hibernate application.
When performing a Criteria hibernate somehow writes data into the database. Debugging through the code we couldn't find any commits to the database driver. Anyways the data could not be rolledback afterwards.
All operations are running in one single hibernate transaction and the corresponding commit/rollback of this transaction is called as expected.

Changing the FlushMode to COMMIT in the Criteria changes this behaviour, but results in the problem that hibernate couldn't find unsaved entities in an other Criteria call.

Any suggestions what to do?

We are using hibernate 3.3.1.GA together with an Oracle 10g database.

Regards
Marco

Hi folk,

we solved the problem. The autocommit from the jdbc driver was active, so the hibernate flush results sometimes in a commit from the jdbc driver. Disabling the autocommit solved the problem.

This were very long and hard hours finding this problem.

Regards,
Marco