| java.lang.Object org.apache.derby.iapi.services.context.ContextImpl org.apache.derby.jdbc.XATransactionState
T0_NOT_ASSOCIATED | final static int T0_NOT_ASSOCIATED(Code) | | |
T1_ASSOCIATED | final static int T1_ASSOCIATED(Code) | | |
TC_COMPLETED | final static int TC_COMPLETED(Code) | | |
TRO_DEADLOCK | final static int TRO_DEADLOCK(Code) | | Rollback-only due to deadlock
|
TRO_FAIL | final static int TRO_FAIL(Code) | | Rollback-only due to end(TMFAIL)
|
associationState | int associationState(Code) | | Association state of the transaction.
|
isPrepared | boolean isPrepared(Code) | | has this transaction been prepared.
|
rollbackOnlyCode | int rollbackOnlyCode(Code) | | |
suspendedList | HashMap suspendedList(Code) | | When an XAResource suspends a transaction (end(TMSUSPEND)) it must be resumed
using the same XAConnection. This has been the traditional Cloudscape behaviour,
though there does not seem to be a specific reference to this behaviour in
the JTA spec. Note that while the transaction is suspended by this XAResource,
another XAResource may join the transaction and suspend it after the join.
|
|
|