IdP 2.3.8 PermGen leak?

[Eric Stein]

I'm seeing a PermGen leak in the 2.3.8 IdP. I'm running it inside Tomcat 6.0.36. When I stop and then start the application, JVisualVM is reporting that the old WebappClassLoader instance isn't unloading. The nearest GC root is a com.mchange.v2.async.ThreadPoolAsynchronousRunner. I'm losing about 15 MB per refresh of the IdP. Is there any way to either (a) configure c3p0 through the IdP so that it doesn't leak memory like a sieve, or (b) use some other thread pool instead? It appears that the most recent IdP (2.4) is still using c3p0 9.1.2, and I'd really rather not have to manually change the jar file in my installations.

Thanks,
Eric Stein

Tomcat Log:

Apr 22, 2014 11:31:17 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading Context with name [/idp] has started
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [net.sf.ehcache.CacheManager at 4b5ed12c] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [Timer-3] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Apr 22, 2014 11:31:17 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/idp] appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak.