Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 56318 invoked from network); 24 Sep 2004 20:22:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 24 Sep 2004 20:22:57 -0000 Received: (qmail 37306 invoked by uid 500); 24 Sep 2004 20:24:57 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 37213 invoked by uid 500); 24 Sep 2004 20:24:56 -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 37166 invoked by uid 99); 24 Sep 2004 20:24:56 -0000 X-ASF-Spam-Status: No, hits=1.6 required=10.0 tests=DNS_FROM_AHBL_RHSBL,DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: 217.160.230.40 is neither permitted nor denied by domain of ian@skylist.net) Received: from [217.160.230.40] (HELO mout.perfora.net) (217.160.230.40) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 24 Sep 2004 13:24:54 -0700 Received: from ian.skylist.net[69.56.37.64] (helo=[69.56.37.64]) by mrelay.perfora.net with ESMTP (Nemesis), id 0MKyxe-1CAwcd2xFW-0004i7; Fri, 24 Sep 2004 16:24:51 -0400 X-Provags-ID: perfora.net abuse@perfora.net b2065fc7c6fcac3e0b687337ee1c599b Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <1592218F4C3EED4FBEAC48F9160FE60F10C953A9@nycexmb09.pfizer.com> References: <1592218F4C3EED4FBEAC48F9160FE60F10C953A9@nycexmb09.pfizer.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ian Ragsdale Subject: Re: Connection leak Date: Fri, 24 Sep 2004 15:24:50 -0500 To: "Apache Torque Users List" X-Mailer: Apple Mail (2.619) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N We recently had a similar problem. Here's what we did, which appeared to alleviate the problem without addressing the underlying connection leak: # don't wait indefinitely for a connection torque.dsfactory.scimitar.pool.maxWait = 5000 # allow up to 25 connections in the pool (up from 8) torque.dsfactory.scimitar.pool.maxActive = 25 # remove connections that have been abandoned torque.dsfactory.scimitar.pool.removeAbandoned = true This should postpone running out of connections by adding more and give the pool time to reclaim abandoned connections. There is also a setting to have it track where connections are leaked from, at the expense of a little overhead when opening connections: logAbandoned = true More configuration settings are here: http://jakarta.apache.org/commons/dbcp/configuration.html On Sep 24, 2004, at 3:06 PM, Husek, Paul wrote: > Hello, > > I'm using Torque v3.1 with commons-dbcp connection pooling. I'm > getting > what I believe is a connection leak. After a certain time of my > application > being up and responsive it just hangs. > > Is there anyway I can verify this? E.g. Can I see how many > connections are > left in the pool, how many have been taken and not returned, etc? In > some > places I do a Torque.getConnection() but may not be returning them. > Can I > cause them to be reaped automatically if I forget to return them? > > > > > > Paul > > > --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org