[DERBY-2531] client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.3.1.4
• Component/s: Network Client
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 09/Apr/07 05:50
• Updated: 19/Feb/08 19:14
• Resolved: 15/Oct/07 17:32

Description

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.

Issue Links

• is duplicated by: DERBY-3431 DatabaseMetaData.getConnection returns the wrong connection when using connection pooling
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• relates to: DERBY-2492 convert checkDataSource, checkDataSource30 and checkDriver.java to junit