Okay, so let's say I set my db connection pool size to one, where do I look to
see what connection doesn't get closed like it should? Is there a particular
log file, place to look in the Lambda Probe, etc, and then how do I trace that
to the source code?
My apologies if the answers to these are really obvious, I'm new to this.
Thanks!
Kristen
Quoting "Caldarale, Charles R" <chuck.caldar...@unisys.com>:
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: Connection Pool Exhausted
from my experience setting numActive to 1 is NOT a l/t solution
No one ever suggested it was; it's simply a debugging technique to
make it easier to find the connection leak.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
PROPRIETARY MATERIAL and is thus for use only by the intended
recipient. If you received this in error, please contact the sender
and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
