[
https://issues.apache.org/jira/browse/DERBY-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2420:
---------------------------------
Component/s: JDBC
Bug behavior facts: [Embedded/Client difference]
Triaged for 10.5.2: flagged as embedded/client difference.
> 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: JDBC, Network Client
> Reporter: 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.
