[jbossts-issues] [JBoss JIRA] (JBTM-2748) Prevent JTS bottom-up recovery from rolling back prepared inflowed JCA transactions

[Tom Jenkinson (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2748:
--------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Prevent JTS bottom-up recovery from rolling back prepared inflowed JCA transactions
> -----------------------------------------------------------------------------------
>
>                 Key: JBTM-2748
>                 URL: https://issues.jboss.org/browse/JBTM-2748
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JCA, JTS, Recovery
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>            Priority: Blocker
>             Fix For: 5.next
>
>
> There exists a defect that if a recovering JVM does the following steps:
> doRecoveryScan()
> waitForOrphanInterval()
> doRecoveryScan()
> *Before* XATerminator::recover is called in the root coordinator then bottom-up recovery will be told there is NoTransaction which is infers as a rollback.
> I saw two options, one was to have TransactionCacheItem try to peek in the objectstore for ServerTransaction/JCA classes. The alternative is to add a new recovery module that can load the ServerTransaction/JCA classes periodically so the transaction won't be lost.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)