Mark/T, Román, Guido, and Mark/DE

-----Original Message-----
From: Mark Thomas [mailto:ma...@apache.org] 
Sent: Friday, July 22, 2016 4:54 PM
To: Tomcat Users List
Subject: Re: OutOfMemoryError: PermGen space - SOLVED

On 22/07/2016 19:15, Berneburg, Cris wrote:
> > Mark (Thomas), Román, Guido, and Mark (Eggers)
> > 
> > [SNIP]
> > 
> > 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.
> 
> No need to apologize. Glad we were able to help.

Thank you all for your gracious replies.  :-)

> Tracking down memory leaks is never easy and I would have said
> guiding someone how to do it via e-mail is close to impossible.
> I'm impressed at how quickly you managed to get this fixed.

Well, please don't be *too* impressed, OK?  ;-)  It was you (Mark Thomas) who 
posted how to find memory leaks and hinted at the Log4J shutdown procedures.  
Román suggested using Java VisualVM to grab heap dumps, and Guido recommended 
using Eclipse Memory Analyzer to analyze them.  Finally, it was Mark Eggers who 
posted the link to the Log4J page that detailed the very Log4J shutdown 
procedures I was missing.  You guys made it possible for me to solve my problem 
and saved me a lot of hassle by sharing your past and current experiences!

> As an added bonus we now have some great content in the archives to
> point people to when they are trying to track down memory leaks.

While I felt like I was in danger of flooding the discussion group with 
stream-of-consciousness writing of all the details I tripped over, the archives 
is what I had in mind for some poor soul in the future struggling through the 
same sort of issue.

Also me slightly bending the rules about top-posting: put a short intro at top 
with a BLUF (bottom-line up front) clause to save folks time who did not want 
details, and then full details embedded in the message below for anyone who 
cared to dig deep.

--
Cris Berneburg
CACI Lead Software Engineer


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to