About Unresolved XA Transactions

Column	Description
XID	Unique XID for the transaction. Integration Server created the XID at the beginning of the transaction and wrote it to the XA recovery store; Integration Server also provided the XID to the participating resources, which also stored the information.
Global 2PC State	Global state of the transaction before Integration Server ended. If a state maps to a global state in the javax.transaction.Status interface described in the JTA standard, that mapping is shown below.
	State	Description
	TR_PREPARE_BEGIN	STATUS_PREPARING
	TR_PREPARE_RESOURCE
	TR_PREPARE_RESOURCE_END
	TR_PREPARE_END	STATUS_PREPARED
	TR_COMMIT_BEGIN	STATUS_COMMITTING
	TR_COMMIT_RESOURCE
	TR_COMMIT_RESOURCE_END
	TR_ROLLBACK_BEGIN	STATUS_ROLLING_BACK
	TR_ROLLBACK_RESOURCE
	TR_ROLLBACK_RESOURCE_END
	TR_ROLLBACK_END	STATUS_ROLLED_BACK
	TR_ROLLBACK_ONLY	MARKED_ROLLBACK
	TR_FORGET_RESOURCE
	TR_FORGET_RESOURCE_END
	TR_COMPLETED
	TR_RECOVERY	Integration Server is trying to resolve the transaction.
	TR_UNDEFINED	STATUS_UNKNOWN
Error Message	Error message that Integration Server wrote to the server log before storing the global state of the transaction in the XA recovery store.
Recovery Action Attempted	Action that Integration Server took to try to resolve the transaction. If Global 2PC State is TR_COMMIT_BEGIN, Integration Server tried to commit the transaction. If the global state is any other value, Integration Server tried to roll back the transaction.

Note: Refresh the page at intervals to make sure all uncompleted transactions are listed. Suppose Integration Server tries to resolve an uncompleted transaction but cannot; the transaction will not be listed while Integration Server is trying to resolve it, but if you refresh the page later, the transaction will appear on the list.