tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 50556] improve JreMemoryLeakPreventionListener against leak caused by LdapPoolManager
Date Fri, 07 Jan 2011 23:01:21 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=50556

--- Comment #4 from Sylvain Laurent <slaurent@apache.org> 2011-01-07 18:01:14 EST ---
>I guess you'd only have to do it if com.sun.jndi.ldap.connect.pool.timeout > 0, though
system properties can be changed at runtime, so it might be a good idea to temporarily set
it to 1 if it's currently 0, init the class, then set it back.

I don't think this is a good idea. This would force the leaking thread to be
spawned even in cases where it is never spawned (if
com.sun.jndi.ldap.connect.pool.timeout=0). This property is supposed to be set
on the command line, so that it does not change at runtime.

I committed the fix on trunk, will be ready for 7.0.6

-- 
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message