The server loads the item with the EntityManager which returns Item(id = 1, version = 1, name = “a”), it changes the name and persist Item(id = 1, version = 1, name = “b”). Hibernate increments the version to 2. That’s a misuse of the JPA API, and the root cause of your bug. If … Read more
Normally when you look into optimistic locking you also use a library like Hibernate or an other JPA-Implementation with @Version support. Example could read like this: public class Person { private String firstName; private String lastName; private int age; private Color favoriteColor; @Version private Long version; } while obviously there is no point of adding … Read more
Optimistic Locking is a strategy where you read a record, take note of a version number (other methods to do this involve dates, timestamps or checksums/hashes) and check that the version hasn’t changed before you write the record back. When you write the record back you filter the update on the version to make sure … Read more