Tim,
On 8/29/23 10:33, Scott,Tim wrote:
Hi all,
Thanks for your responses. I think I've found the problem.
My wrapping class which detects the invocation of the close() method to
decrement its count is no longer decrementing its count because
method.getDeclaringClass() has changed from java.
Hi all,
Thanks for your responses. I think I've found the problem.
My wrapping class which detects the invocation of the close() method to
decrement its count is no longer decrementing its count because
method.getDeclaringClass() has changed from java.sql.Connection to
java.lang.AutoCloseable.
Tim,
On 8/25/23 10:48, Scott,Tim wrote:
Hi John,
Why does your app need 20 connections just to start up? That's a
bit of a rhetorical question, but needing so many connections to
start up seems odd to me.
It doesn't. It only needs 1-2 at a time, but it makes 100s of queries
in loops, each ti
Hi John,
> Why does your app need 20 connections just to start up? That's a bit of a
> rhetorical question, but needing so many connections to start up seems odd to
> me.
It doesn't. It only needs 1-2 at a time, but it makes 100s of queries
in loops, each time using a connection from t
Tim,
> -Original Message-
> From: Scott,Tim
> Sent: Friday, August 25, 2023 3:09 AM
> To: users@tomcat.apache.org
> Subject: DataSource Connection pool leak
>
> Hi,
>
> For various diagnostics, I tried Tomcat 9.0.79 recently on a development
> machine. It
Hi,
For various diagnostics, I tried Tomcat 9.0.79 recently on a development
machine. It didn't solve the problem I was experiencing - that was later
identified as a problem in IntelliJ with remote deployment and is not why I'm
mailing.
I tweaked my Tomcat 9.0.79 configuration to start my appl
