Torsten,
On 4/17/23 19:31, Torsten Krah wrote:
Use logAbandoned as a boolean parameter
+1
remoteAbandoned is only a band-aid; you need to fix your application.
In development, I always run with maxTotal="1" and logAbandoned="true"
and maxWaitMillis="1". This will help you find
We stumbled into it to be honest. There should be a fairly easy way though
if you're on a linux box... something like..
grep -r ".getConnection" * should get you all the classes that make a call
to something like sqlConn.getConnection(), and then once you have that you
can check for finally {}
Use logAbandoned as a boolean parameter, you will get stacktraces in the
log. From those you can narrow down where you are leaking connections.
Akshay Mishra schrieb am Di., 18. Apr. 2023,
01:07:
> Hello Tomcat Community!
>
>
> Tomcat Version: 9.0.70
>
> Our Tomcat web service started
my team saw this same thing in production - there was code that never
closed the SQL connection after it was created... 150+ connections spike
all at once, took out the pool. Not sure if that's your issue, but thought
i'd mention it
Kevin Huntly
Hello Tomcat Community!
Tomcat Version: 9.0.70
Our Tomcat web service started exhausting the max connections allowed to the
backend datastore (Postgres).
>From the logs, we don’t see any 1 thread requesting lot of connections. Nor do
>we see too many threads requesting a new connection.
We
