[jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery
Michael Musgrove (JIRA)
issues at jboss.org
Fri May 23 08:32:59 EDT 2014
Michael Musgrove created JBTM-2183:
Summary: Need finer grained control over which XAResource is used for recovery
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.0.1, 4.17.20
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 4.17.21, 5.0.2
During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery.
However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user".
The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) .
And finally, I I wonder if we want to make this new behaviour optional?
This message was sent by Atlassian JIRA
More information about the jbossts-issues