[
https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3431:
-----------------------------------
Derby Info: (was: [Patch Available])
Thank you for the comments Knut Anders.
I'll have a look at them and try to finalize the patch today.
Regarding the test nit, I'll remove it. Note that embedded currently returns
the same reference there, causing the assertNotSame to fail. It doesn't matter
though, as the method is supposed to throw the "No current connection"
exception.
> 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.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.3, 10.5.0.0
> Environment: Client-server with connection pooling enabled.
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3431-1a-test_repro.diff,
> derby-3431-1b-test_repro.diff, derby-3431-2a-test.diff,
> derby-3431-3a-client_logical_metadata.diff,
> derby-3431-3a-client_logical_metadata.stat
>
>
> 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.
