While modifying a record in the database through hibernate API update function, I get "StaleObjectStateException" error sometimes.

The full error message is:

WARNING: An operation failed due to stale data
net.sf.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect)



I am doing optimistic concurreny check for this table through one timestamp field in the table. And this timestamp value, I am not changing while each updation of the record. I am keeping it same. Can that be causing this issue ? I mean if I make this timestamp field to be automatically generated at DB side while any modification, it might work out.

Please provide me any pointers to resolve the issue.

Mostly I don't use timestamps, but the specific <version> tag. Something along the lines of:



And in the java code something like:



The version is automatically updated by Hibernate. You don't have to touch it yourself. Everytime your object is saved, you should see in the database a version update.

If Hibernate finds a mismatch (because somebody else updated the row), Hibernate will throw the "StaleObjectStateException".

Regards,

Jos