If you have ever used Tomcat for development purposes for more than 10 minutes (especially within Eclipse), you certainly have encountered the infamous messag “OutOfMemoryError: PermGen space”, and the only solution was to restart Tomcat.
Despite the fact that you should be aware that such message may indicate a deeper problem, there is an easy’n dirty solution via JVM options. I have come to the fix after browsing the Interwebs for a while, and your luck may vary. The solution consists in setting up the following set of JVM arguments:
-server -XX:+DisableExplicitGC -XX:MaxPermSize=256m -XX:PermSize=256m -XX:MaxNewSize=256m -XX:NewSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled
I have added them all for the sake of laziness, although the last three are said to be used with caution (especially the last one)
Setting up within Eclipse
Even in 2012 I still use the Sysdeo Tomcat Plugin because of its simpliciy over Eclipse’s WTP Servers. Open Window -> Preferences (Command + , if you are using a Mac) and go to Tomcat -> JVM Settings -> Append to JVM parameters.
Setting up Tomcat standalone
Another approach is to add the arguments directly to Catalina.sh. Locate it in Tomcat’s bin directory and set the JAVA_OPTS variable, like this:
JAVA_OPTS="-XX:+DisableExplicitGC -XX:MaxPermSize=256m -XX:PermSize=256m -XX:MaxNewSize=256m -XX:NewSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled"
Just restart Tomcat and you should be good to go.