[jira] Updated: (DERBY-2420) XAConnection close method should throw an exception if it is called when the global transaction is associated with the connection.

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

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

Myrna van Lunteren updated DERBY-2420:
--------------------------------------

    Fix Version/s:     (was: 10.3.0.0)

Unsetting fix version. If it still makes it into 10.3, appropriate fix version can be set when resolving.

> XAConnection close method should throw an exception if it is called when the global transaction is associated with the connection.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2420
>                 URL: https://issues.apache.org/jira/browse/DERBY-2420
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>            Reporter: Julius Stroffek
>            Assignee: Julius Stroffek
>            Priority: Minor
>
> As comments show in DERBY-2220 The Distributed Transaction Processing: The XA Specification forbids for a transaction manager or an application to call XAConnection.close method when there is a global transaction associated with the XA connection.
> Currently,
> Embedded driver throws the exception but the connection is left in a state when it cannot be used anymore and the locks held by the transaction can not be released later.
> Network driver allows the call of the method and closes the connection.

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