<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 02/09/2012 09:34 AM, Geoffrey De Smet wrote:
<blockquote cite="mid:jh00e5$6v6$1@dough.gmane.org" type="cite">
<pre wrap="">The perm gen space is a subset of the heap space.
So it doesn't make sense to put them on the same value.
Try this instead:
-Xmx1024m -XX:MaxPermSize=512m
Or, if that fails:
-Xmx2048m -XX:MaxPermSize=1024m
</pre>
</blockquote>
Sorry to disagree Geoffrey, but PermGen is NOT a part of heap in all
(Sun) JVM's that I'm aware of. See<br>
<br>
<a class="moz-txt-link-freetext" href="http://stackoverflow.com/questions/2129044/java-heap-terminology-young-old-and-permanent-generations">http://stackoverflow.com/questions/2129044/java-heap-terminology-young-old-and-permanent-generations</a><br>
<a class="moz-txt-link-freetext" href="http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html">http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html</a> (the
picture a few pages down)<br>
<br>
So the sizes are specified separately. But having a MaxPerm of 1G
and STILL see PermGen OOM is strange.<br>
<br>
The problem could be, that when using the CMS (concurrent mark
sweep) GC, PermGen is not collected. I have seen cases where sooner
or later OOM PermGen errors happened consistently, until we added <br>
<br>
<code>-XX:+CMSPermGenSweepingEnabled</code><br>
<pre class="moz-signature" cols="72">--
CU, Joe</pre>
</body>
</html>