JWM wrote:
Two things you can do here.
1. Set both removeAbandoned and logAbandoned parameters to
true. This will reclaim most lost connections. And log a trace of what
code called a connection that was never closed.
2. Use a finally block to close all of your Resultsets and
getting successfully
closed?
Thx.
JWM
-Original Message-
From: Brian Cook [mailto:[EMAIL PROTECTED]
Sent: Friday, October 07, 2005 3:38 PM
To: Tomcat Users List
Subject: Re: Tracking Datasource Connection Usage?
JWM wrote:
Two things you can do here.
1. Set both removeAbandoned
Brian Cook wrote:
JWM wrote:
Two things you can do here.
1. Set both removeAbandoned and logAbandoned parameters to
true. This will reclaim most lost connections. And log a trace of
what code called a connection that was never closed.
See, I don't get all this removeAbandoned
http://findbugs.sourceforge.net/
Will tell you where in your code you are not freeing resources.
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
-Original Message-
From: JWM [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 2:09 PM
To:
Hi,
On 6 Oct 2005 at 15:09, JWM wrote:
I started getting exceptions saying no connections were available on my JDBC
datasource (org.gjt.mm.mysql.Driver). The pool was definitely large enough
to handle the load. So it appears that I'm not freeing the all the
connections as I should. I
Rob Hills wrote:
I started getting exceptions saying no connections were available on my JDBC
datasource (org.gjt.mm.mysql.Driver). The pool was definitely large enough
to handle the load. So it appears that I'm not freeing the all the
connections as I should. I noticed that I did not
