Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
10.1.3.1, 10.2.1.6, 10.3.2.1, 10.4.1.3
-
None
-
None
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:org.apache.derby.client.am.LogicalConnection@11b9fb1stmt.getConnection():org.apache.derby.client.net.NetXAConnection@540408
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-3431 DatabaseMetaData.getConnection returns the wrong connection when using connection pooling
- Closed