From torque-user-return-5681-apmail-db-torque-user-archive=db.apache.org@db.apache.org Thu Dec 23 17:02:28 2004 Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 97032 invoked from network); 23 Dec 2004 17:02:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Dec 2004 17:02:28 -0000 Received: (qmail 81475 invoked by uid 500); 23 Dec 2004 17:02:19 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 81450 invoked by uid 500); 23 Dec 2004 17:02:19 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 81429 invoked by uid 99); 23 Dec 2004 17:02:19 -0000 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_POST,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mail-kan.bigfish.com (HELO mail45-R-kan.bigfish.com) (63.161.60.29) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 23 Dec 2004 09:02:15 -0800 Received: from mail45-kan.bigfish.com (localhost.localdomain [127.0.0.1]) by mail45-R-kan.bigfish.com (Postfix) with ESMTP id E0E6C11CB75 for ; Thu, 23 Dec 2004 17:02:12 +0000 (UCT) X-BigFish: VPC Received: by mail45-kan (MessageSwitch) id 1103821332834970_14460; Thu, 23 Dec 2004 17:02:12 +0000 (UCT) Received: from mailrelay6.pfizer.com (ns11.pfizer.com [192.77.198.11]) by mail45-kan.bigfish.com (Postfix) with ESMTP id A997A11CB48 for ; Thu, 23 Dec 2004 17:02:12 +0000 (UCT) Received: from nycexcn02.pfizer.com (localhost [127.0.0.1]) by mailrelay6.pfizer.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id iBNH29ij005413 for ; Thu, 23 Dec 2004 12:02:09 -0500 (EST) Received: by NYCEXCN02.pfizer.com with Internet Mail Service (5.5.2654.89) id ; Thu, 23 Dec 2004 12:06:36 -0500 Message-ID: <1592218F4C3EED4FBEAC48F9160FE60F137645F9@nycexmb09.pfizer.com> From: "Husek, Paul" To: torque-user@db.apache.org Subject: connection leak Date: Thu, 23 Dec 2004 12:01:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4E911.089EE184" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C4E911.089EE184 Content-Type: text/plain Hello, I'm using torque 3.1 and am experiencing what I believe to be a connection leak. The symptoms are that eventually the application just stops responding and seems to be stuck where it would normally be fetching a db connection. This is probably due to the fact that I occasionally need to construct my own queries and do a Torque.getConnection, and due to errors may not be able to release the connection. I've seen mention of abandoned connection management via DBCP, but I could never get it working. I just upgraded to dbcp 1.2, and I still can't get it working. Does anyone have a Torque.properties that properly handles abandoned connections (and has been verified)? ------_=_NextPart_001_01C4E911.089EE184--