[DERBY-3431] DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.5.1.1
• Component/s: JDBC, Network Client
• Environment: Client-server with connection pooling enabled.
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 19/Feb/08 10:12
• Updated: 04/May/09 18:22
• Resolved: 02/Jun/08 10:30

Description

The connection returned from DatabaseMetaData.getConnection is not the same as the connection used to create the meta data object when the client driver is used with connection pooling enabled.
For trunk, the embedded driver/ds does the right thing.

Issue Links

• duplicates: DERBY-2531 client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.
• is part of: DERBY-1018 Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection