[ http://issues.apache.org/jira/browse/DERBY-339?page=all ]
Kathey Marsden resolved DERBY-339:
----------------------------------
Resolution: Fixed
> 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.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-339
> URL: http://issues.apache.org/jira/browse/DERBY-339
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Fix For: 10.1.0.0
> Attachments: derby339.diff
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
