public class TransactionTimeoutException extends LockConflictException
This exception is not thrown if a deadlock is detected, even if the
timeout elapses before the deadlock is broken. If a deadlock is detected,
DeadlockException is always thrown instead.
The transaction timeout interval may be set using
Transaction handle is invalidated as a result of this
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
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.