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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.2.0
• Component/s: JDBC, Network Client
• Labels: derby_triage10_9
• Urgency: Normal
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Julius Stroffek
• Created: 08/Mar/07 15:11
• Updated: 20/Feb/12 22:18

Description

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.

Issue Links

• relates to: DERBY-246 XA end() fails with Connection is closed error

Sub-Tasks

• implement the finalize method separately (currently, the close method is called) for both client and network drivers.: Closed