[
https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570340#action_12570340
]
myrna edited comment on DERBY-3431 at 2/19/08 9:55 AM:
--------------------------------------------------------------------
I think this is a duplicate of DERBY-2531, which is a duplicate of DERBY-1018?
was (Author: myrna):
I think this is a duplicate of DERBY-2531?
> DatabaseMetaData.getConnection returns the wrong connection when using
> connection pooling
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-3431
> URL: https://issues.apache.org/jira/browse/DERBY-3431
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Environment: Client-server with connection pooling enabled.
> Reporter: Kristian Waagan
> Priority: Minor
> Attachments: derby-3431-1a-test_repro.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
