> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com] > Subject: Re: How to start a daemon without getting the warning?
> But I can't detect any obvious Thread.getContextClassLoader() > calls in the code below: The problem isn't associated with calling the above method, it's actually that the webapp's classloader has been associated with your thread. If you reset the contextClassLoader for your thread, that /might/ avoid the memory leak when the webapp is stopped. However, if the thread retains any references to other webapp-related classes, you still have the leak. Best to manage your threads properly - which is a good bit trickier in a container environment than in a stand-alone program. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
