db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (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.
Date Thu, 09 Jun 2005 06:07:05 GMT
Mamta Satoor wrote:

> Hi Kathey,
>  
> I looked at the patch and it looks good. I just have the same question
> as on the previous patch. Why
> has conn_.setXAState(Connection.XA_LOCAL); been moved in from various
> places to the end() method in NetXAResource?
>  

Thanks Mamta.

I went ahead and checked this in.

The end() method  is used to indicate the end of the transaction branch
association per table 6-2 of the XA+ specification, State Table for
Transaction Branch Association.
http://www.opengroup.org/onlinepubs/8095979699/toc.pdf
which says association ends at xa_end, This change brings the state
transition into line with the specification. It was incorrect for
XA_LOCAL to be set on commit() and rollback().  It should have been ha
penning in end().

There are two changes related to the state changes.

DERBY-246 - Initial patch that removed most of the XA state  leaving XA_LOCAL and XA_GLOBAL
state but had some incorrect state handling in commit and rollback.
http://svn.apache.org/viewcvs.cgi?view=rev&rev=179867

DERBY-339 - Change XA_LOCAL and XA_GLOBAL to have a better mapping to the XA+ specification.
Fix setting of state for commit/rollback/end and exceptions.
XA_TO_NOT_ASSOCIATED 
XA_T1_ASSOCIATED 

http://svn.apache.org/viewcvs.cgi?view=rev&rev=189710



Thanks

Kathey




Mime
View raw message