public interface XAOutflowHandle
 In certain circumstances, if all outflowing transactions forget the enlistment or it is owned by another node,
 the transaction may be resolved at prepare directly with an XA_RDONLY status, or it may be completely
 removed from the transaction before it completes, allowing more efficient transaction resolution as well as
 correct behavior in the presence of outflow cycles.
| Modifier and Type | Method and Description | 
|---|---|
static XAOutflowHandle | 
createSimple(Xid xid,
            int timeout)
Create a simple, no-operation outflow handle. 
 | 
void | 
forgetEnlistment()
Signal that this enlistment may be forgotten. 
 | 
int | 
getRemainingTime()
Get an estimated remaining timeout for this transaction. 
 | 
Xid | 
getXid()
Get the XID of the transaction. 
 | 
void | 
nonMasterEnlistment()
Signal that the peer already had the transaction in question. 
 | 
void | 
verifyEnlistment()
Signal that this enlistment should be activated effective immediately. 
 | 
int getRemainingTime()
void forgetEnlistment()
void nonMasterEnlistment()
void verifyEnlistment()
               throws RollbackException,
                      SystemException
RollbackException - if the transaction was rolled back before the enlistment could be activatedSystemException - if the enlistment failed for an unexpected reason@NotNull Xid getXid()
null)static XAOutflowHandle createSimple(Xid xid, int timeout)
xid - the transaction ID (must not be null)timeout - the estimated remaining time, in secondsnull)Copyright © 2017 JBoss by Red Hat. All rights reserved.