[jbossts-issues] [JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete
[
https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson commented on JBTM-860:
------------------------------------
+1 - and would recommend a docs JBEAP issue if it is not reflected accurately in the EAP
docs.
Narayana is a opensource community project which is integrated into a number of containers
(opensource or commercial), for example: WildFly, EAP, Spring, Karaf, Tomcat. Issues can
be resolved here but still have downstream problems (in this case it seems an issue in EAP
docs).
Thanks for your interest in Narayana - if there is anything more we can do to help feel
free to comment on issue or in our forums or IRC - there are some good links here:
http://narayana.io/community/index.html
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
(v7.5.0#75005)