[
https://issues.apache.org/jira/browse/DERBY-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas resolved DERBY-1018.
----------------------------------
Resolution: Duplicate
It appears to me that this bug has been fixed by the work on related issues.
> Client xa Statement.getConnection and DatabaseMetadata.getConnection returns
> underlying NetXAConnection instead of Logical connection
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1018
> URL: https://issues.apache.org/jira/browse/DERBY-1018
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.2.1, 10.4.1.3
> Reporter: Kathey Marsden
> Attachments: ClientXADataSourceTest.java
>
>
> 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.logicalconnect...@11b9fb1stmt.getconnection():org.apache.derby.client.net.netxaconnect...@540408
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
