public class OptimisticLockingException extends ConcurrentAccessException
concurrent access exception that indicates that the repository can not acquire optimistic locks for some of the locally modified objects.
It's usually possible and adequate to attempt to commit the transaction again (optimistic strategy).
Pessimistic locks can help to avoid the problematic situation (see also CDOAutoLocker) at commit time.
The optimistic locking timeout can be configured on the server side:
<property name="optimisticLockingTimeout" value="10000"/>
| Constructor and Description |
|---|
OptimisticLockingException(String message) |
isLocal, wrapaddSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toStringpublic OptimisticLockingException(String message)
Copyright (c) 2011-2015 Eike Stepper (Berlin, Germany) and others.