[
https://issues.apache.org/jira/browse/DERBY-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4141:
----------------------------------
Attachment: derby-4141_diff.txt
The attached patch (derby-4141_diff.txt) has the client and embedded changes
and adds a test for the XAER_RMFAIL case. I couldn't figure out a case for
testing the XAER_RMERR case, (non-session ending exception that causes an xa
operation to fail), but if anyone has any ideas, please let me know and I'll
add a test for that too.
For client I mapped the disconnect exception to XAException.XAER_RMFAIL and
verified that server side exceptions that cause XAExceptions do indeed get the
errorCode from the server. I think this resolves my concerns about client side
SQLExcetptions.
Running tests now. I would like to backport this change to 10.3. It is a
behavior change, but I think a sensible one that is low risk. Please let me
know if you have any concerns.
> XAExceptions thrown by Derby can have errorCode 0
> --------------------------------------------------
>
> Key: DERBY-4141
> URL: https://issues.apache.org/jira/browse/DERBY-4141
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.3.0, 10.4.2.0, 10.5.1.1,
> 10.6.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Attachments: derby-4141_diff.txt, derby-4141_embbeded_diff1.txt
>
>
> When an XAException occurs during xa.start() or other XA operation, because
> of an SQLException, we have an errorCode of 0, regardless of the severity. I
> would suggest XAER_RMFAIL for SESSION_SEVERITY or greater and XAER_RMERR for
> lower severity exceptions. See thread
> http://www.nabble.com/XAException.errorCode-on-XAException-caused-by-an-SQLException-tt22832423.html
> for more detail and a reproduction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
