[
https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin...
]
Tom Jenkinson commented on JBJCA-1244:
--------------------------------------
Further information that is pertinent to the implementation of this defect is that after
discussion with Jesper on the forum, the reason that LocalXAResourceImpl has difficulty in
determining the underlying cause of the rollback exception is that the errorcode parameter
in LocalTransactionException does not have a defined value to indicate communication
issues so a way to formalise this code should be found:
https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.0.30.Final/...
LocalXAResourceImpl returns RBROLLBACK in certain scenarios which
violate the XA specification
----------------------------------------------------------------------------------------------
Key: JBJCA-1244
URL:
https://issues.jboss.org/browse/JBJCA-1244
Project: IronJacamar
Issue Type: Bug
Affects Versions: 1.0.30.Final
Reporter: Tom Jenkinson
Assignee: Jesper Pedersen
The XA specification states the following about the RBROLLBACK error code for
xa_commit():
{quote}
[XA_RB∗]
The resource manager did not commit the work done on behalf of the transaction branch.
Upon return, the resource manager has rolled back the branch’s work and has released all
held resources. These values may be returned only if TMONEPHASE is set in flags:
[XA_RBROLLBACK]
The resource manager rolled back the transaction branch for an unspecified reason
{quote}
It is clear that the RBROLLBACK code may only be returned if the branch is known to have
rolled back (and indeed if the onePhase flag is set to true).
To cater for scenarios where the XAResource is not able to determine the outcome of the
resource managers commit. In those scenarios the XA specification is clear that the only
legal error code to return is:
{quote}
[XAER_RMFAIL]
An error occurred that makes the resource manager unavailable.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)