Mark (Thomas), Román, Guido, and Mark (Eggers) Thank you all for your suggestions, assistance, and patience.
With your help and encouragement I learned how to perform heap dumps using Java VisualVM, analyze them using Eclipse Memory Analyzer, and follow instructions. ;-) The OutOfMemoryError in Tomcat Manager was caused by a memory leak when Log4J did not terminate properly. This was due to my mistake of neglecting to set up the necessary Log4J shutdown procedures. Adding Log4jServletContextListener and log4jServletFilter to my app's web.xml solved the problem. The Find Leaks button on the Tomcat Manager page confirmed. I apologize for taking your time and bandwidth on such a newbie mistake. Thanks again for your help. :-) -- Cris Berneburg CACI Lead Software Engineer -----Original Message----- From: Berneburg, Cris [mailto:cberneb...@caci.com] Sent: Thursday, July 14, 2016 2:27 PM To: Tomcat Users List Subject: OutOfMemoryError: PermGen space > Hi Folks > > I got this error from the Tomcat Web Application Manager after having > stopped and started one of the applications multiple times. (This was > after repeatedly deploying the application manually to attempt to find > a bug that I could not reproduce in my IDE.) Once the error occurred, > the server was extremely sluggish to respond even to remote desktop > mouse and keyboard events. [SNIP] > Here's the error: > > FAIL - Application at context path /someapp could not be started > FAIL - Encountered exception java.lang.OutOfMemoryError: PermGen space > > Is this likely due to a memory leak in my application? [SNIP] > OS: Win Server 2012 R2 > Java: 1.6.0_24 (oops, need to upgrade that now) > Tomcat: 6.0.37 (hmm... will need to upgrade soon-ish) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
