I've managed to get rid of PermGen space errors using this JVM startup
configuration:
-XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=128m
Hope that might help others affected by this problem.
On Fri, May 10, 2013 at 2:15 PM, nhhockeyplayer nashua <
nhhockeypla...@hotmail.
With my maven pom.xml settings setup like This...
${jetty-maven-plugin-version}
${mysql.groupId}
${mysql.artifactId}
${mysql.jConnect.JDBC.version}
Thanks guys for the helpful feedback.
I am not sure if my latest corrupted markup bug could be a biproduct of this
memory mauling.
yes I am in development mode on a live deployment under tomcat and mysql jetty
jdbc
it happened on the live server... so I was cussin a few over it
Here is a blip
If you're running in development mode and have made a lot of iterative
changes to page/component/mixin/service classes since the last restart (a
lot being dozens or hundreds, depending on your MaxPermSize setting), this
can be considered normal. Tapestry's live class reloading does chew up
permgen
It means that you dont have enough memory for the application
try running the application with something like -XX:MaxPermSize=128M
On Wed, May 8, 2013 at 7:18 PM, nhhockeyplayer nashua <
nhhockeypla...@hotmail.com> wrote:
> Folks,
>
> has anyone seen this? ANy ideas how to remedy ?
>
> HTTP Sta
