[DERBY-339] Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.1.1.0
• Component/s: Network Client
• Assignee: Katherine Marsden
• Reporter: Katherine Marsden
• Created: 07/Jun/05 01:21
• Updated: 26/Jan/06 02:01
• Resolved: 09/Jun/05 15:19

Description

Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be defered to the server.

The client tries to track XA state to make decisions based on current XA state. Most of this state handling was removed with DERBY246, but it still was not being handled properly. This is evidenced by multiple failures in xaSimplePostive that now that it gets past DERBY-246.

This fix will have the client track only branch association as outlined in the XA+ specification. Table 6-2, State Table for Transaction Branch Association. The client will track only

XA_TO_NOT_ASSOCIATED
XA_T1_ASSOCIATED

Association Suspended (T2) will map to XA_TO_NOT_ASSOCIATED for the client's pupurposes.

The client commit in autocommit mode only for
XA_TO_NOT_ASSOCIATED.

Issue Links

• incorporates: DERBY-246 XA end() fails with Connection is closed error