[jbossts-issues] [JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

[Ondřej Chaloupka (JIRA)]

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

Ondřej Chaloupka commented on JBTM-860:
---------------------------------------

This issue seems to be connected with https://bugzilla.redhat.com/show_bug.cgi?id=1010242 as the in-flow connection does not register JNDI name to Xid eisname and it could cause problems in case of recovery for this case. See comments on bugzilla to find detailed info.
                
> use XAResourceWrapper metadata for assume complete
> --------------------------------------------------
>
>                 Key: JBTM-860
>                 URL: https://issues.jboss.org/browse/JBTM-860
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Resource Manager
>    Affects Versions: 4.15.0
>            Reporter: Jonathan Halliday
>            Assignee: Tom Jenkinson
>             Fix For: 6.0.0.Final
>
>
> In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM.  It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control.  With the availability of RM id information from XAResourceWrapper this becomes feasible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira