[
https://issues.apache.org/jira/browse/DERBY-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-5167:
----------------------------------
Component/s: JDBC
marking component as jdbc as first guess where problem might be. Could be in
store also, but has feel of issue in the jdbc interface code.
> Attempting to XAResource.end an xid that timed out / rolled back internally
> in the DB will give the wrong XA error
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5167
> URL: https://issues.apache.org/jira/browse/DERBY-5167
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.6.2.1
> Reporter: Guy Pardon
>
> See https://issues.apache.org/jira/browse/DERBY-5166:
> If after the scenario described there, we try to call XAResource.end for any
> of the Xids involved, we get errors like this:
> XA resource 'derbyXADB1': end for XID
> '3139322E3136382E302E34352E746D30303030313030303139:3139322E3136382E302E34352E746D31'
> raised -4: the supplied XID is invalid for this XA resource
> javax.transaction.xa.XAException
> However, since the xid was (presumably) rolled back after timeout in the DB,
> the correct error should be one of the XA_RB* error codes, rather than this
> confusing one?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
