public class LockPreemptedException extends LockConflictException
Transaction handle is invalidated as a
result of this exception.
Locks may be preempted in a JE HA environment on a Replica system when the HA write operation needs a lock that an application reader transaction or cursor holds. This exception is thrown by a reader transaction or cursor method that is called after a lock has been preempted.
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, 2016 Oracle and/or its affiliates. All rights reserved.