LockConflictExceptionas the common base class for lock conflict exceptions.
public class DeadlockException extends LockConflictException
EnvironmentConfig.LOCK_OLD_LOCK_EXCEPTIONSis set to true.
set to true, see below)
DeadlockException is not thrown by JE
because true deadlock detection is not used in JE. Currently, lock timeouts
are used instead, and a deadlock will cause a
When true deadlock detection is added to JE in the future,
DeadlockException will be thrown instead of
when a true deadlock occurs.
For compatibility with JE 3.3 and earlier,
thrown instead of
EnvironmentConfig.LOCK_OLD_LOCK_EXCEPTIONS is set to true. This
configuration parameter is false by default. See
EnvironmentConfig.LOCK_OLD_LOCK_EXCEPTIONS for information on the changes
that should be made to all applications that upgrade from JE 3.3 or
Normally, applications should catch the base class
LockConflictException rather than catching one of its subclasses. All lock
conflicts are typically handled in the same way, which is normally to abort
and retry the transaction. See
LockConflictException for more
Transaction handle is invalidated as a result of this
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
Copyright (c) 2002, 2015 Oracle and/or its affiliates. All rights reserved.