[
https://issues.apache.org/jira/browse/DERBY-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saurabh Vyas updated DERBY-2531:
--------------------------------
Attachment: ConnPoolErr.java
Attached a repro for this issue. Did a comparison on object created earlier &
then returned by s.getConnection().
I 'll start looking into this in depth, if any one with more Knowledge on
ConnectionPoolDataSource can give some pointers it would be great help.
Thanks in advance
> 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.0.0
> 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.
