So, yesterday, I finally start working on upgrading on old application set to a current 6 release of Tomcat.
(Sigh, behind the truck already, seeing the announcement of the next version today bad timing by me... beside the point) Some of my web applications are using JFreeChart to generate images. Even though I'm using the -Djava.awt.headless=true flag, Tomcat is still telling this upon shutdown: SEVERE: The web application [/ap] appears to have started a thread named [AWT-Windows] but has failed to stop it. This is very likely to create a memory leak. How does one handle this properly? It isn't a critical issue for me, since we never undeploy / redeploy anyway, without restarting the entire server. But now it is just annoying me. Someone must have had to deal with this before? I can't figure out how I can either prevent the JVM from creating this thread, or how to get the JVM to let the thread end. I haven't dug for it yet, but I assume there is a switch I can use to shut off the memory detect warnings? (If I can't figure out how to fix all my issues) I can't ship code to the customers that logs "SEVERE" errors on shutdown. Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
