<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/11/13 6:23 PM, Joshua Riffle
wrote:<br>
</div>
<blockquote
cite="mid:CACmOZFryfneujH_FnN-F2QiQaDP=NWERXq=Xu3y--0SY7W3NAQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>We have been getting this error from time to time
with our Shibboleth Identity Provider in Tomcat 6 and
before you reply to this thread...<br>
<br>
</div>
1) Yes I know this is caused by a memory leak and can be
'mitigated' by increasing the max permgen size: <a
moz-do-not-send="true"
href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare</a><br>
<br>
</div>
2) Or better yet possibly resolved in Tomcat 7: <a
moz-do-not-send="true"
href="http://wiki.apache.org/tomcat/MemoryLeakProtection">http://wiki.apache.org/tomcat/MemoryLeakProtection</a><br>
<br>
</div>
-- What I don't know and would LOVE input on is:<br>
<br>
</div>
1) How do you detect or prevent the evil PermGen error
beforehand? My understanding is increasing the MaxPermGenSize
is only delaying the inevitable memory leak build up.<br>
<br>
</div>
2) Better yet: Best practices? What have you already done in
your architecture to avoid or defeat this kind of issue?<br>
</div>
</blockquote>
<br>
<font face="tahoma, sans-serif">Restarting just the IdP-context
(deploying new war) only has caused fatal leakage (to effectively
crash tomcat) for me, if done repeatedly. That is, a few times in
a few minutes.</font><br>
<br>
Using ecmascript in the resolver caused leakage from hell into
permgen for me. Porting scripts to type mapped or template got rid
of that.<br>
</body>
</html>