IdP 2.3.8 PermGen leak?

[Eric Stein]

Thanks for replying, Scott.



Using the Container-managed connection did step on that permgen leak.



-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Tuesday, April 22, 2014 2:57 PM
To: Shib Users
Subject: Re: IdP 2.3.8 PermGen leak?



On 4/22/14, 2:47 PM, "Eric Stein" <steine at locustec.com<mailto:steine at locustec.com>> wrote:



>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.



For the record, we don't really support reloading.



> 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?



Configure a container-managed data source and then you can use any data source you prefer. I use dbcp.



-- scott





--

To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140423/db0ce2da/attachment-0001.html