Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 95155 invoked from network); 3 Nov 2010 17:43:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Nov 2010 17:43:27 -0000 Received: (qmail 22458 invoked by uid 500); 3 Nov 2010 17:43:55 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 22264 invoked by uid 500); 3 Nov 2010 17:43:55 -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 22255 invoked by uid 99); 3 Nov 2010 17:43:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 17:43:54 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of barry.l.propes@citi.com designates 85.158.136.227 as permitted sender) Received: from [85.158.136.227] (HELO mail162.messagelabs.com) (85.158.136.227) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 17:43:46 +0000 X-VirusChecked: Checked X-Env-Sender: barry.l.propes@citi.com X-Msg-Ref: server-11.tower-162.messagelabs.com!1288806202!6852954!1 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [199.67.141.124] Received: (qmail 4509 invoked from network); 3 Nov 2010 17:43:23 -0000 Received: from mail.citigroup.com (HELO mail.citigroup.com) (199.67.141.124) by server-11.tower-162.messagelabs.com with AES256-SHA encrypted SMTP; 3 Nov 2010 17:43:23 -0000 Received: from imbhub-gt02.nam.nsroot.net ([169.171.119.172]) by smtpinbound.citigroup.com (Switch-3.4.1/Switch-3.4.1) with ESMTP id oA3HhMWM001409 for ; Wed, 3 Nov 2010 17:43:22 GMT Received: from exlnjiht02.lac.nsroot.net (EXLNJIHT02.lac.nsroot.net [150.110.183.30]) by imbhub-gt02.nam.nsroot.net (Switch-3.4.1/Switch-3.4.1) with ESMTP id oA3HhLxI003558 for ; Wed, 3 Nov 2010 17:43:21 GMT Received: from exnjht03.nam.nsroot.net (150.110.165.223) by exlnjiht02.lac.nsroot.net (150.110.183.30) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 3 Nov 2010 13:43:21 -0400 Received: from exlgtcht01.lac.nsroot.net (168.72.74.51) by exnjht03.nam.nsroot.net (150.110.165.223) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 3 Nov 2010 13:43:20 -0400 Received: from exgtmb06.nam.nsroot.net ([169.171.98.118]) by exlgtcht01.lac.nsroot.net ([168.72.74.51]) with mapi; Wed, 3 Nov 2010 12:43:19 -0500 From: "Propes, Barry L " To: "'Tomcat Users List'" Date: Wed, 3 Nov 2010 12:43:16 -0500 Subject: RE: Connection Leak Thread-Topic: Connection Leak Thread-Index: Act7cvnmzCi0648DS4mKVtnbAUXnOwAC3nLQ Message-ID: <08382548D50D3049BD5599E1E3146B34110B936BE3@exgtmb06.nam.nsroot.net> References: <08382548D50D3049BD5599E1E3146B34110B93695D@exgtmb06.nam.nsroot.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-WiganSS: 01000000010019exlnjiht02.lac.nsroot.net ID0044<08382548D50D3049BD5599E1E3146B34110B936BE3@exgtmb06.nam.nsroot.net> I had a bit of a leak, and it stopped them...actually an error coupled with= a leak. You might check with some of the other users -- I think they've recommended= Lamda Probe and some other tools to track down leaks. -----Original Message----- From: Ziggy [mailto:ziggy25@gmail.com]=20 Sent: Wednesday, November 03, 2010 11:19 AM To: Tomcat Users List Subject: Re: Connection Leak Does that show cached queries? On Wed, Nov 3, 2010 at 4:02 PM, Propes, Barry L wr= ote: > Maybe try adding this, too as an attribute in the Resource tag. > > timeBetweenEvictionRunsMillis=3D"-1" > > -----Original Message----- > From: Jason Britton [mailto:jbritton31@gmail.com] > Sent: Wednesday, November 03, 2010 9:05 AM > To: Tomcat Users List > Subject: Re: Connection Leak > > Since you're using an Oracle database - another way to identify areas=20 > in your code that aren't closing connections. In the sql below=20 > substitute YOURDBUSER with the name of the database user your=20 > connections connect to your database with and YOURWEBSERVER with the=20 > name of your webserver. The results of the sql query will give you=20 > the last executed sql for each of the open connections. Then search=20 > your code for where this sql is being executed and double check you are c= losing the connection appropriately. > > SELECT username, machine, oc.sql_text, COUNT(*) open_statements FROM=20 > v$session vs, v$open_cursor oc WHERE username =3D 'YOURDBUSER' AND=20 > machine =3D 'YOURWEBSERVER' AND oc.sid =3D vs.sid GROUP BY username,=20 > machine, oc.sql_text ORDER BY open_statements DESC > > > > On Wed, Nov 3, 2010 at 6:44 AM, Ziggy wrote: > > > Hi All, > > > > > type=3D"javax.sql.DataSource" > > driverClassName=3D"oracle.jdbc.driver.OracleDriver" > > url=3D"jdbc:oracle:thin:@10.10.10.10.:1521:mydb" > > username=3D"username" password=3D"password" maxActive=3D"5= 00" > > maxIdle=3D"50" > > maxWait=3D"-1" removeAbandoned=3D"true" > > removeAbandonedTimeout=3D"60" logAbandoned=3D"true" > > accessToUnderlyingConnectionAllowed=3D"true" > > /> > > > > I am trying to find out areas of the application where connections=20 > > are NOT being closed. I added the removeAbandoned and logAbandoned=20 > > clauses in my context file but if i check v$session on oracle it is=20 > > still showing the same number of connections active even after 60 secon= ds. > > Is there something wrong in the configuration above? > > > > > > How exactly does it abandone the connections? what triggers it>? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org