[
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 for a
cycle 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, there is a filter that checks for transaction state
(JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore
this Xid so adding this protection would only be considered belt-and-braces.
was:
If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline for a
cycle 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, there is a filter that checks for transaction state which would detect a
transaction log and ignore this Xid so adding this protection would only be considered
belt-and-braces.
Orphan detection may attempt to rollback orphan if resource fails to
return values
----------------------------------------------------------------------------------
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 for a
cycle 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, there is a filter that checks for transaction state
(JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore
this Xid so adding this protection would only be considered belt-and-braces.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)