db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2406) XAResource.end does not set the XA transaction state correctly when the XAException is thrown
Date Thu, 08 Mar 2007 11:08:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-2406:
--------------------------------------

    Derby Info:   (was: [Patch Available])

Thanks Julo! The comment looks useful to me. Committed revision 516009.

> XAResource.end does not set the XA transaction state correctly when the XAException is
thrown
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2406
>                 URL: https://issues.apache.org/jira/browse/DERBY-2406
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.3.0.0
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: d2406.diff
>
>
> 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);
>         } 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message