Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 71198 invoked from network); 21 Nov 2007 06:15:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Nov 2007 06:15:54 -0000 Received: (qmail 32101 invoked by uid 500); 21 Nov 2007 06:15:37 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 31403 invoked by uid 500); 21 Nov 2007 06:15:35 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 31394 invoked by uid 99); 21 Nov 2007 06:15:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Nov 2007 22:15:35 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of phil.steitz@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2007 06:15:23 +0000 Received: by nf-out-0910.google.com with SMTP id d3so2064422nfc for ; Tue, 20 Nov 2007 22:15:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=oLqjEnmP3EwpOLAm+xdSsXkhlUEPKhU0C1IlmcMdLOs=; b=Syk67gdNo04pcQG3dqdpse9zQN2UT/B/cAZ6GUabzy+dwfY2eUd2zopFxrby50Vkzm/HT3x90dmWYKtZdqmunDeVuj0jtI/9t+jhdD+3wNSJCDfLdXwLMKpUeI4WeuWP/vBn9M0ftto+0VYoNxF5q1t/7FH6c+UbyoWHKW4rlD0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sJ/eCT/tRSwGjwZuHdfkZmGjxoJMKUpbuT4P9Q9cebY176yK9ZSxLK6k1IpDNQ40x18ue74IT0jE4FyTGwbkR1XT0Ywvq4M3ucPEyBVw6TErylCwGJ27PA/mYAWMoDSa0kbBJcQcsn706iF1T8SdrE6JwlKapwW84il3NHNHP1I= Received: by 10.78.184.2 with SMTP id h2mr7712667huf.1195625715732; Tue, 20 Nov 2007 22:15:15 -0800 (PST) Received: by 10.78.130.13 with HTTP; Tue, 20 Nov 2007 22:15:15 -0800 (PST) Message-ID: <8a81b4af0711202215t7419056avbd18c4039f988286@mail.gmail.com> Date: Tue, 20 Nov 2007 23:15:15 -0700 From: "Phil Steitz" To: "Jakarta Commons Users List" Subject: Re: Re: [dbcp] Error when closing a connection (maybe DBCP-216?) In-Reply-To: <8a81b4af0711192239w1129c219yc0e5a45a74531f7d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8a81b4af0711192239w1129c219yc0e5a45a74531f7d@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org After running some tests and looking carefully again at the stack traces above, I think that while removing the listener on destroy per DBCP-216 is a good idea and will resolve this problem, the reason that it has not been reported up to now is most likely that (assuming I am understanding the stack traces correctly - unfortunately I can find no documentation for the Sybase classes) the driver is indirectly generating a questionable connectionClosed event when the SybPooledConnection closes the SybConnectionProxy. See http://bugs.mysql.com/bug.php?id=884 for an argument for why this is questionable. IIUC, your second stack trace (triggered by destroyObject) matches the bug repoorted there. In any case, we should clean up listeners better in DBCP. I will do that. Thanks again for reporting this. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org