I have actually seen errors similar to these too, [quote]SEVERE: The web application [/public] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.[/quote]
What I came to realize was that Tomcat was not releasing system resources upon shutdown. This was especially problematic with IDE integration in Netbeans/Eclipse. When I'd stop/start Tomcat and redploy between builds, the first or second restart of Tomcat were fine. After 3 or 4, there were problems. I found that after rebooting my dev box I could once again start Tomcat properly and would not encounter those errors anymore. I tried using IntelliJ instead of Netbeans and I haven't encountered the problem again. I did see it once on a production box, but went to the old reboot trick and it worked. Didn't see it ever again, so I'm not sure what exactly caused it. But it makes me fear deployment on Tomcat. Almost want to say, "bump it" and start deploying on JBoss or some other application server. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=f3b8e656-fc02-4fe4-bf40-98d40bdfb9db ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
