Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80097 invoked from network); 2 Jun 2008 10:32:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jun 2008 10:32:08 -0000 Received: (qmail 75213 invoked by uid 500); 2 Jun 2008 10:32:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 74992 invoked by uid 500); 2 Jun 2008 10:32:10 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 74981 invoked by uid 99); 2 Jun 2008 10:32:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 03:32:10 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 10:31:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id EE862234C12E for ; Mon, 2 Jun 2008 03:31:44 -0700 (PDT) Message-ID: <562244268.1212402704975.JavaMail.jira@brutus> Date: Mon, 2 Jun 2008 03:31:44 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling In-Reply-To: <612085556.1203415963849.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3431. ------------------------------------ Resolution: Fixed Marking as resolved, awaiting test runs (and other feedback) for confirmation of the fix. > 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, derby-3431-3b-client_logical_metadata.diff, derby-3431-4a-spt_test_nit.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.