[DERBY-2406] XAResource.end does not set the XA transaction state correctly when the XAException is thrown

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Network Client
• Urgency: Normal
• Assignee: Julius Stroffek
• Reporter: Julius Stroffek
• Created: 06/Mar/07 10:47
• Updated: 08/Mar/07 13:20
• Resolved: 08/Mar/07 13:20

Description

As the comments in DERBY-2360 show when calling the XAResource.end the XAException may be thrown even when the transaction was successfully disassociated from the connection but the transaction was marked as rollback only. The code at the end of XAResource.end function does not handle this correctly. It either throws an XAException or sets the connection state to XA_T0_NOT_ASSOCIATED. The corresponding code from NetXAResource.end method is

if (rc != XAResource.XA_OK)

{ throwXAException(rc, false); }

else

{ conn_.setXAState(Connection.XA_T0_NOT_ASSOCIATED); }