[DERBY-1018] Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.1.3.1, 10.2.1.6, 10.3.2.1, 10.4.1.3
• Component/s: JDBC, Network Client
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 22/Feb/06 03:58
• Updated: 12/Jan/11 22:24
• Resolved: 21/Jul/09 15:57

Description

For client XA a Statement.getConnection() and DatabaseMetaData.getConnection() return a NetXAConnection instead of a LogicalConnection.

e.g. for a connection obtained from a ClientXADataSource:

Statement stmt = conn.createStatement();
System.out.println("conn:" + conn + "stmt.getConnection():" + stmt.getConnection());

yields

conn:[e-mail]():org.apache.derby.client.net.NetXAConnection@540408

Issue Links

• incorporates: DERBY-3431 DatabaseMetaData.getConnection returns the wrong connection when using connection pooling