db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4141) XAExceptions thrown by Derby can have errorCode 0
Date Thu, 09 Apr 2009 21:50:13 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697664#action_12697664
] 

Kathey Marsden commented on DERBY-4141:
---------------------------------------

I see am.SqlCode has the disconnect exception at 40000, so I could use XAER_RMFAIL for those
but I think that severe exceptions from the server don't get that code.


> 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_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.


Mime
View raw message