Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5167

Attempting to XAResource.end an xid that timed out / rolled back internally in the DB will give the wrong XA error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 10.6.2.1
    • None
    • JDBC
    • Normal
    • Deviation from standard

    Description

      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?

      Attachments

        Activity

          People

            Unassigned Unassigned
            guypardon Guy Pardon
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: