[jbossts-issues] [JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

[Ondra Chaloupka (JIRA)]

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

Ondra Chaloupka commented on JBTM-2907:
---------------------------------------

per discussion with David and Tom the way of fixing JBEAP-11528 is to implement {{doRecover}} in JTS XATerminatorImple. The {{XATerminator.recover}} call from RAR is then provided to call {{doRecover(null,null}} which returns all subordinate in-doubt transactions which is expected.

> Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2907
>                 URL: https://issues.jboss.org/browse/JBTM-2907
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS
>    Affects Versions: 5.6.1.Final, 5.5.24.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Blocker
>
> When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}},  {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case.
> The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/jca/XATerminatorImple.java#L511). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)