Andre Thenot wrote:
I've been noticing the following error when deploying my cocoon WAR more
than about 6-7 times without restarting the app server. This stack trace
occurs on OS X and on Linux with JDK 1.5.0 in both cases. I am running
JBoss 4.2.2GA; the memory settings are -Xms128m -Xmx512m.
Should I be restarting the app server every time I deploy the app or is
this a leak for which I need to gather more information for an eventual
bug report?
This is a well-known problem, caused by the non-removal of Proxy classes
from the permanent generation portion of the Sun JVM memory.
Proxy classes are mainly generated by frameworks using AOP: Hibernate,
Spring, etc., and, of course, from the applications using such AOP
frameworks, like Cocoon 2.2.
No matter how much you increase your PermGenSpace, sooner or later you
will hit the wall (every redeploy decreases the amount of PermGenSpace
available).
Solutions ?
1) You may try to use the BEA JRockit JVM, which doesn't suffer from
this particular problem (I switched to it for my Eclipse instance and
lived happy thereafter).
2) You may stick to Sun JVM and just live with it in development (not
many redeploy in Cocoon 2.2, after all), and in production too (there's
a very limited need to redeploy in production, right ?).
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
