hi Nicholas,
where is your pool configured? In server.xml or in your application context?
If it is configured in server.xml, then this is a bug, the thread should have
been created with the class loader from the pool itself.
If it is configured in the application context, then this simply means you forgot to call DataSource.close on the connection pool when your
web application is stopped.
best
Filip
On 3/2/2011 8:32 PM, Nicholas Sushkin wrote:
Hi, Filip,
Is there a recommended way to clean up after the pool? I am getting the
following error message and I wonder if I need to add some code to prevent
memory leak.
2011-03-02 22:20:20,786 ERROR [http-8081-1]
org.apache.catalina.loader.WebappClassLoader - The web application [/…]
appears to have started a thread named [[Pool-Cleaner]:Tomcat Connection
Pool[19-2018147830]] but has failed to stop it. This is very likely to create
a memory leak.
Thanks.
ps. Also, thanks for offering to open a Bugzilla enhancement request for
setting password via JMX.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
