You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/02/21 19:59:29 UTC
[jira] Created: (DERBY-1018) Client xa Statement.getConnection and
DatabaseMetadata.getConnection returns underlying NetXAConnection instead
of Logical connection
Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection
--------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-1018
URL: http://issues.apache.org/jira/browse/DERBY-1018
Project: Derby
Type: Bug
Components: Network Client
Versions: 10.2.0.0, 10.1.2.3, 10.1.3.0
Reporter: Kathey Marsden
Fix For: 10.1.3.0
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1018) Client xa Statement.getConnection and
DatabaseMetadata.getConnection returns underlying NetXAConnection instead
of Logical connection
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-1018:
---------------------------------
Attachment: ClientXADataSourceTest.java
Attaching ClientXADataSourceTest.java, which demonstrates that this bug has been fixed.
> 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.LogicalConnection@11b9fb1stmt.getConnection():org.apache.derby.client.net.NetXAConnection@540408
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1018) Client xa Statement.getConnection and
DatabaseMetadata.getConnection returns underlying NetXAConnection instead
of Logical connection
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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:org.apache.derby.client.am.LogicalConnection@11b9fb1stmt.getConnection():org.apache.derby.client.net.NetXAConnection@540408
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1018) Client xa Statement.getConnection and
DatabaseMetadata.getConnection returns underlying NetXAConnection instead
of Logical connection
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1018?page=all ]
Kathey Marsden updated DERBY-1018:
----------------------------------
Fix Version: (was: 10.1.3.0)
> Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1018
> URL: http://issues.apache.org/jira/browse/DERBY-1018
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.2.0.0, 10.1.2.3, 10.1.3.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:org.apache.derby.client.am.LogicalConnection@11b9fb1stmt.getConnection():org.apache.derby.client.net.NetXAConnection@540408
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1018) Client xa Statement.getConnection and
DatabaseMetadata.getConnection returns underlying NetXAConnection instead
of Logical connection
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ 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.LogicalConnection@11b9fb1stmt.getConnection():org.apache.derby.client.net.NetXAConnection@540408
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.