Mark (Eggers) and Mark (Thomas) BLUF: Memory leak found and fixed. I did not set up the necessary Log4J shutdown procedures. Please see below.
-----Original Message----- From: Mark Eggers [mailto:its_toas...@yahoo.com.INVALID] Sent: Thursday, July 21, 2016 8:32 PM To: Tomcat Users List Subject: Re: OutOfMemoryError: PermGen space > > From the log4j2 web site: > > > > https://logging.apache.org/log4j/2.x/manual/webapp.html [SNIP] > > If you are using Log4j in a Servlet 2.5 web application, or if you > > have disabled auto-initialization with the > > isLog4jAutoInitializationDisabled context parameter, you must > > configure the Log4jServletContextListener and Log4jServletFilter in > > the deployment descriptor or programmatically. > > *** I did not do that at all. Is it the context listener's responsibility > for shutting down properly? Why the filter is needed? Guess I'll set them > up and see if that makes a diff. That fixed it. Adding Log4jServletContextListener and log4jServletFilter to my web.xml solves the problem. The Find Leaks button on the Tomcat Manager page confirms. Chalk it up to a newbie error. Thanks for your help and patience. :-) -- 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
