Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 83982 invoked from network); 9 Mar 2011 17:35:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Mar 2011 17:35:10 -0000 Received: (qmail 56589 invoked by uid 500); 9 Mar 2011 17:35:06 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 56486 invoked by uid 500); 9 Mar 2011 17:35:06 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 56477 invoked by uid 99); 9 Mar 2011 17:35:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2011 17:35:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.22.94.67] (HELO virtual.halosg.com) (72.22.94.67) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2011 17:34:58 +0000 Received: (qmail 16226 invoked from network); 9 Mar 2011 11:34:35 -0600 Received: from dsl093-126-130.den1.dsl.speakeasy.net (HELO ?192.168.26.66?) (66.93.126.130) by halosg.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 9 Mar 2011 11:34:35 -0600 Message-ID: <4D77BA2A.60503@hanik.com> Date: Wed, 09 Mar 2011 10:34:34 -0700 From: Filip Hanik - Dev Lists User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc11 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Cleaning up after tomcat jdbc-pool? References: <4D6FBF27.50103@hanik.com> <201103041059.42461.nsushkin@openfinance.com> <201103061259.26698.nsushkin@openfinance.com> <4D74B818.40503@apache.org> <4D74FC5A.4090406@hanik.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 03/07/2011 06:46 PM, Nicholas Sushkin wrote: > I don't think the default pool has any glaring leaks. However, your db may. > I have ran into cases when Oracle would run out of PGA memory, which cleared > with tomcat restart. > > It may help to use connection validation feature of tomcat's new pool to > close connections that ran out of memory. > Look at the "maxAge" property in http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html it is created just to deal with the database sessions that have memory leaks, and the leak is somewhat predictable timing wise best Filip > Don't know if such a scenario has been tested. I am curious to hear. > > On Mar 7, 2011 10:46 AM, "הילה" wrote: > > Thanks :] > Let's see if it'll somewhat help with the memory leak, or with memory > management at all > > > 2011/3/7 Filip Hanik - Dev Lists > > > >> On 3/7/2011 3:48 AM, Mark Thomas wrote: >> >> >>> On 07/03/2011 10:39, הילה wrote: >>> >>> >>>> I found this... >>>> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org