This exception is used by the lock manager to indicate that it detected a deadlock.
It prevents the deadlock by throwing this exception. Typically,
this deadlock is a result of the following scenario: one transaction owns a
weaker lock as a result of getting a map entry, and then, at commit time,
the transaction attempts to promote the weaker lock to a stronger
lock in order to apply the changes to the data store.
For example, two transactions try to promote from shared locks to
exclusive locks but each transaction already owns a shared lock.
Constructs a new LockDeadlockException with null as its detail
message. The cause is not initialized, and may subsequently be initialized
by a call to the initCause method.
Constructs a new LockDeadlockException with the specified detail message. The
cause is not initialized, and may subsequently be initialized by a call to
the initCause method.
Parameters:
message - the detail message. The detail message is saved for later
retrieval by the getMessage method.