[JBoss JIRA] (JBTM-2885) Orphan detection may attempt to rollback XID even if XAR did not report Xid due to failure
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2885?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2885:
--------------------------------
Description:
If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time.
However, the filter that checks for transaction state should detect a transaction log and ignore this Xid anyway.
was:If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time.
> Orphan detection may attempt to rollback XID even if XAR did not report Xid due to failure
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-2885
> URL: https://issues.jboss.org/browse/JBTM-2885
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Priority: Optional
> Fix For: 5.next
>
>
> If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time.
> However, the filter that checks for transaction state should detect a transaction log and ignore this Xid anyway.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months