Problem with tomcat hanging on Shib 2.4

[Brian Koehmstedt]

I am almost positive that PermGen does NOT come out out of heap.  
Actually, I can confirm this as I am looking at JVM stats now that are 
showing me perm is indeed separate.

John, based on the documentation, I believe caching is off by default, 
and we have not added any of the caching options, so I believe that 
attribute resolver caching is not in play here at thus not at fault.

On 8/29/2014 11:40 AM, Cantor, Scott wrote:
> On 8/29/14, 2:10 PM, "John Kamminga" <jkamminga at ucmerced.edu> wrote:
>> Scott, our traffic has increased and I'd like to explore the 'caching
>> attribute resolution results for too long'. Where is this configured? In
>> multiple places? And, what is the default that is shipped with Shibboleth
>> Idp?
> https://wiki.shibboleth.net/confluence/display/SHIB2/ResolverRDBMSDataConne
> ctor
> https://wiki.shibboleth.net/confluence/display/SHIB2/ResolverLDAPDataConnec
> tor
>
> There are no defaults, none of the connectors in the example file matter
> much to anybody running a real IdP.
>
> If it's true that permgen space comes out of the same heap maximum, that's
> news to me, but I run with
> -Xmx768m -XX:MaxPermSize=512m and have never had a problem. I cache
> connector results for a few minutes.
>
> If you ever get an OutOfMemory error in the log, you don't need to waste
> time looking for other explanations.
>
> -- Scott
>