Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have an entity class that uses @Version.
@Version
protected Long auditVersion;
What if there are two threads both trying to insert the first occurrence of the entity? Both instances of the entity will have auditVersion set to null. It seems that Hibernate does not take any notice of the optimistic locking fail, I do not get the StaleObjectStateException I expected.
Why not?
Because optimistic locking is used to handle concurrent updates and removals. If two threads try to insert two entities with the same ID, the unique constraint on the primary key is sufficient to detect the conflict. No need for optimistic locking for this.