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

Alon Greenland (JIRA) issues at jboss.org
Thu Jan 18 02:57:00 EST 2018

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

Alon Greenland commented on JBTM-860:

this issue is marked as resolved for almost 3 years now. The fix doesn't state any conditions under which it is not complete. Also, the linked Narayana team [blog post|http://jbossts.blogspot.com.au/2011/07/norecoveryxa.html] doesn't indicate any such conditions.

However, in the latest EAP 7.1 [documentation|https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html-single/development_guide/index#limitations_of_the_xa_recovery_process] under "Limitations of the XA Recovery Process" for this issue it states:

 "JBoss EAP 7.1 has an implemented enhancement to clear transaction logs after a successfully committed transaction and the above situation should not occur frequently."

It indicates that the fix doesn't fully fix the issue and that the issue can still occur under certain conditions. 

Any info about what these conditions are, in case this entry in the documentation is correct?

> use XAResourceWrapper metadata for assume complete
> --------------------------------------------------
>                 Key: JBTM-860
>                 URL: https://issues.jboss.org/browse/JBTM-860
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: Resource Manager
>    Affects Versions: 4.15.0
>            Reporter: Jonathan Halliday
>            Assignee: Gytis Trikleris
>             Fix For: 5.1.0
> 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 was sent by Atlassian JIRA

More information about the jbossts-issues mailing list