Hi,
I use Tomcat 4.0.1 with the parameter reloadable=true for my webapp.
I have a problem with my Database Connection Pool when Tomcat Reloading this Context
after install new classes or *.jar.
My connections are not destroy by tomcat and remain latency but my ConnectionPool
can't use its.
So,
Can you destroy it in your initialization servlet's destroy method?
-Original Message-
From: Guillaume Albini [mailto:[EMAIL PROTECTED]
Sent: March 20, 2003 6:32 AM
To: [EMAIL PROTECTED]
Subject: Problem with a Database ConnectionPool
Hi,
I use Tomcat 4.0.1 with the parameter
:[EMAIL PROTECTED]
Sent: March 20, 2003 6:32 AM
To: [EMAIL PROTECTED]
Subject: Problem with a Database ConnectionPool
Hi,
I use Tomcat 4.0.1 with the parameter reloadable=true for my webapp.
I have a problem with my Database Connection Pool when Tomcat Reloading this
Context after install new classes
Have same problem.
When classes are reloaded, number of DB connections
exceeds the max number of connections allowed.
crashing my DB server.
Any fixes?
Thanks.
__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your