db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling
Date Wed, 21 May 2008 15:09:55 GMT

     [ 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-3a-client_logical_metadata.stat
                derby-3431-3a-client_logical_metadata.diff

'derby-3431-3a-client_logical_metadata.diff' introduces a logical database metadata object
in the client driver.
One such object will be created (on demand) for each logical connection. In general it only
forwards method calls to the metadata object of the underlying physical connection. If the
logical connection is closed, it will not forward the calls even if the underlying physical
connection is still open.

Besides general comments / review, a few points to look at:
 * LogicalDatabaseMetaData.detach : Is this required / worth the hassle?
 * What about unwrap / isWrapper for?
 * The logicalCon.isClosed() check in getRealMetaDataObject - can it ever happen?

Regression tests run without failures (except for the SetTransactionIsolation:embedded error).
Patch ready for review.

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


Mime
View raw message