I am getting the following error:

.....Message_Error : 'com.x.exceptions.PtRuntimeException: CallResult: addException():org.springframew
ork.orm.hibernate3.HibernateOptimisticLockingFailureException: Batch update returned unexpected row count from update [0
]; actual row count: 0; expected: 1; nested exception is org.hibernate.StaleStateException: Batch update returned unexpe
cted row count from update [0]; actual row count: 0; expected: 1

---
This is what I am trying to do:

Every now and then I issue a delete statement. I do not know if there are any rows in the database that will actually be deleted or not. There may be a row deleted, there may be 0 rows deleted.

If there are actually 0 rows to be deleted, I see the error above. Hibernate assumes that this is an error. Is there a way to tell hibernate to not assume that it is an error and keep going if it deleted 0 rows?

thanks

JavaTek

I believe you get this error when the objects in the Hibernate Session don't match the database.

This can happen due to multiple threads accessing the same objects, database rollbacks etc.

For example, I can cause this error as follows:
1) Let Hibernate transaction time out after 'saving' objects. This causes an exception. Database is rolled back but session still thinks the object has been updated.
2) Do an update on the same objects. Hibernate assumes that the object is in the database and throws the error when it doesn't find it.

To solve the problem, I changed to use merge instead of update. This commits your changes without assuming that the database and session are in line. Alternatively, you could try catching the exception, closing and clearing the session and retrying the transaction.