[jira] Updated: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

["Kristian Waagan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-3431:
-----------------------------------

    Attachment: derby-3431-1b-test_repro.diff

'derby-3431-1b-test_repro.diff' is almost identical to 1a except for some minor tweaks.
Only the test for embedded has been enabled, as the test fails with the client driver.

Committed 'derby-3431-1b-test_repro.diff' to trunk with revision 658181.

> 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
>
>
> 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.