Jon- A couple of things that may be of immediate use to you (even for older releases) Confine your variables to have as restricted scope as possible in other words If you have a number of JSP tags that are application scope and get by with request then convert those tags to use request scope If you're using 1.. n new allocations inside of a method use gc() at the end of that method to force the garbage collector to recover the allocations for profiler try http://pmd.sourceforge.net/ which will easily integrate with Ant or Maven builds..
Feel free to follow up with any specific questions I hope this helps you, Martin This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents ----- Original Message ----- From: "Mark Thomas" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Monday, November 27, 2006 8:37 PM Subject: Re: Memory leaks on webapp redeploy > Jon Miller wrote: >> Hi all, >> >> Is anyone running into issues with memory leaks occuring whenever a >> webapp is redeployed? > > Tomcat version? There have been issues with older releases. > >> I think I read in a FAQ that even using a singleton in your app will >> cause memory leaks? Does anyone know if this is true? > > It depends on how careful you are using it. There are lots of ways to > write code that leaks memory. > > Rather than try guessing where the leak is, get yourself a profiler > and find it. > > Mark > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
