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)" <ji...@apache.org> on 2007/10/15 19:32:51 UTC
[jira] Closed: (DERBY-2531) client returns different connection on
s.getConnection() on a statement obtained from a ConnectionPoolDataSource
or XADataSource than the original connection.
[ https://issues.apache.org/jira/browse/DERBY-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-2531.
---------------------------------
Resolution: Duplicate
Duplicate of DERBY-1018
> client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2531
> URL: https://issues.apache.org/jira/browse/DERBY-2531
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.1.4
> Reporter: Myrna van Lunteren
> Attachments: ConnPoolErr.java
>
>
> In the following scenario:
> ClientXADataSource dsx = new ClientXADataSource();
> dsx.setDatabaseName(dbName);
> XAConnection xac = dsx.getXAConnection();
> XAResource xar = xac.getXAResource();
> Connection cs1 = xac.getConnection();
> Statement sru1 = cs1.createStatement();
> sru1.setCursorName("SN1");
> sru1.executeUpdate("insert into intTable values 1,2,3");
> Connection conn2 = s.getConnection();
> When using an EmbeddedXADataSource, cs1 and conn2 are the same connection. However with Client they're not.
> Found during conversion of test checkDataSource to DataSourceTest.java.
> If this difference is correct, or acceptable, it should get documented...
> With DerbyNetClient, they're not the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.