org.hzero.core.exception.OptimisticLockException: error.optimistic lock

The OptimisticLockException is a type of exception that occurs when two or more transactions attempt to modify the same data simultaneously, and the database system detects a conflict. In other words, when one transaction tries to modify a record, the database checks to see if the record has been modified by another transaction since the first transaction read it. If so, the database system raises an OptimisticLockException to indicate that the data has been changed by another transaction, and the first transaction needs to retry its operation.

This exception is commonly encountered in systems that use optimistic locking to handle concurrent access to shared data. Optimistic locking is a technique used to prevent conflicts between concurrent transactions by allowing them to proceed independently until they try to commit their changes. At that point, the system checks if the data has been modified by another transaction and, if so, raises an exception.

The OptimisticLockException is typically handled by retrying the operation that caused the exception. To avoid the exception, systems can use pessimistic locking instead of optimistic locking, which prevents concurrent access to shared data by locking the data before any transaction can modify it. However, this approach can result in lower concurrency and performance, as it restricts access to shared data.