https://issues.apache.org/bugzilla/show_bug.cgi?id=50556
Summary: improve JreMemoryLeakPreventionListener against leak
caused by LdapPoolManager
Product: Tomcat 7
Version: 7.0.5
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: sylvain.laur...@gmail.com
When class com.sun.jndi.ldap.LdapPoolManager is initialized, if if the system
property com.sun.jndi.ldap.connect.pool.timeout is set to a value greater than
0, a PoolCleaner thread is spawned, without fixing a specific context class
loader.
If the initialization of the class is triggered by a web application, its class
loader will be used by the PoolCleaner thread. If that web app is stopped, its
class loader will leak.
We can improve JreMemoryLeakPreventionListener to prevent that leak.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
