[jbossts-issues] [JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

Mark Little (JIRA) issues at jboss.org
Thu Sep 18 04:10:02 EDT 2014


    [ https://issues.jboss.org/browse/JBTM-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003746#comment-13003746 ] 

Mark Little commented on JBTM-2255:
-----------------------------------

StatusChecker.getStatus checks the object store (see bottom of method) using getStatus on the OTS factory if instance isn't running. Make sure that checks the object store location where logs may be moved in the event of assumed complete scanner going off.

> Do not return StatusCommiting, if transaction was commited by the original transaction manager
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2255
>                 URL: https://issues.jboss.org/browse/JBTM-2255
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>             Fix For: 4.17.23
>
>
> We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing.
> However, as shown by the attached bugzilla, another work flow is also possible. Because Oracle database returned XAException.XAER_RMFAIL, second resource was committed successfully and the client was told that the transaction committed successfully. Recovery was left to sort out the issue with the database. Once the database resource invoked replay_completion and transaction manager saw the status of the transaction as StatusCommitted, it assumed that it is still in action even though there is no BasicAction available.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbossts-issues mailing list