[
https://issues.apache.org/jira/browse/DERBY-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Stroffek updated DERBY-2420:
-----------------------------------
Fix Version/s: 10.3.0.0
I think this issue is worth while fixing before 10.3 release. I'll went through
code and it should not be difficult to fix this. I'll create a patch at the
beggining of the next week.
> 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
> Fix For: 10.3.0.0
>
>
> 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.
