Chris, The way I thought it worked was if I configured
'RemoveAbandonedOnBorrow' and RemoveAbandonedTimeout="15" was that each
time I requested a new connection from the pool, any connections that
had been idle for >15 minutes and had not been returned by my code to
the pool would be recovered,
Jerry,
On 12/4/21 23:06, Jerry Malcolm wrote:
I had a db connection leak in my code where an error condition would
throw an exception and bypass the connection cleanup code. I found that
and fixed it. But before I found the problem, my program was
overrunning the max connections and locking o
Jon,
On 12/6/21 10:28, Jonathan Yom-Tov wrote:
I have a single instance of Tomcat (version 9.0.54) in which the thread
count on a connector thread pool doesn't reduce despite most of the threads
(198/200) being idle. If I understand correctly the default idle time
before a thread is reaped is 60
