[
https://issues.apache.org/jira/browse/DERBY-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-1018:
-----------------------------------
Component/s: JDBC
Affects Version/s: 10.4.0.0
10.3.2.1
Updating affected versions based on a new bug report (duplicate, DERBY-3431).
> 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.0.0
> Reporter: Kathey Marsden
>
> 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:[EMAIL PROTECTED]():[EMAIL PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
