I too have found this problem. I dont entirely understand it myself, but I was told that when you restart / stop-start a webapp tomcat has to create new classloaders - and the old classloaders are orphaned and are not cleaned up during garbage collection, so you basically get a memory leak. In my experience the size of the leak depends on the complexity of the program - ie a struts app using dozens of libraries (itext, fop, ojb, quartz, axis, jdom, xerces, etc) will cause a bigger memory leak that a tiny servlet using no libraries.
I dont think the problem is tomcat specific - ie i believe it affects other servlet containers aswell. So, using remote shell access to restart tomcat saves a lot of trouble. Daniel. > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] Behalf Of Thomas Kellerer > Sent: 04 November 2004 12:33 > To: [EMAIL PROTECTED] > Subject: Re: Remotely restart Tomcat. > > > On 04.11.2004 12:49 Christoph Kutzinski wrote: > > > AFAIk this is generally disrecommended in production environments since > > there are some memory leaks in Tomcat/Struts (which are seemingly very > > hard or impossible to fix) regarding webapp restart. > > > > The recommended way is to shut down and restart tomcat. > > > > For a develop environment webapp restart is ok. > > > > HTH > > Christoph > > > Do you have any reference (documents, links) for this? > > Thomas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
