Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 94117 invoked from network); 6 May 2005 13:56:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 May 2005 13:56:59 -0000 Received: (qmail 56254 invoked by uid 500); 6 May 2005 13:56:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 56185 invoked by uid 500); 6 May 2005 13:56:15 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 56155 invoked by uid 99); 6 May 2005 13:56:14 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from e31.co.us.ibm.com (HELO e31.co.us.ibm.com) (32.97.110.129) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 06 May 2005 06:56:14 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j46DrHua280412 for ; Fri, 6 May 2005 09:53:23 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j46DrH3w293792 for ; Fri, 6 May 2005 07:53:17 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j46DrCJY024544 for ; Fri, 6 May 2005 07:53:12 -0600 Received: from [127.0.0.1] (sig-9-48-122-61.mts.ibm.com [9.48.122.61]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j46DrBkI024482 for ; Fri, 6 May 2005 07:53:12 -0600 Message-ID: <427B76C6.3090802@debrunners.com> Date: Fri, 06 May 2005 06:53:10 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: Pooled connections are closed? References: <427AA471.7020807@sun.com> <001801c551c8$04d4ef60$0200000a@lan> <427AAA14.8020307@sun.com> In-Reply-To: <427AAA14.8020307@sun.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N David Van Couvering wrote: > Well, more information on this. It appears if I call getConnection() > twice on the *same* XAConnection or PooledConnection(), the first > connection is closed as soon as I get the second connection. I am not > sure if this is a bug. Not a bug, defined by the JDBC spec. Extract from JDBC 3.0 section 11.4 "Any previously existing Connection object is automatically closed when the associated PooledConnection.getConnection method is called." Dan.