[jbossts-issues] [JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

[Anonymous (JIRA)]

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

Issue was automatically transitioned when pull request #957 was created in GitHub
---------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Try to contact the transaction status connection manager 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: Feature Request
>          Components: Recovery
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 5.later
>
>
> 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.
>  
> There are a couple of advantages to this:
> 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely
> 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended)



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