[jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBTM-2583:
-----------------------------------------------

Petr Penicka <ppenicka at redhat.com> changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from VERIFIED to CLOSED

> Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2583
>                 URL: https://issues.jboss.org/browse/JBTM-2583
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Recovery
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 4.17.34, 5.2.17.Final, 5.3.0.Final
>
>
> Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager.
> This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back.
>  
> * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely
> * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed



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