On 10.06.2011 16:55, Caldarale, Charles R wrote: >> From: April Easton [mailto:aeas...@shawneecourt.org] >> Subject: Tomcat shutdown issues > >> I don't see any of my threads in there > > Look harder: > >> "Worker-JM" prio=3D10 tid=3D0x000000005d7a1800 nid=3D0x521f in Object.wait() >> at >> org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:58) >> "Bundle File Closer" daemon prio=3D10 tid=3D0x000000005e223800 nid=3D0x521d >> in Object.wait() >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:397) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:333) >> "Start Level Event Dispatcher" daemon prio=3D10 tid=3D0x000000005d5fc000 >> nid=3D0x521b in Object.wait() >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:397) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:333) >> "Framework Event Dispatcher" daemon prio=3D10 tid=3D0x000000005d956800 >> nid=3D0x521a in Object.wait() >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:397) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:333) > > Those aren't Tomcat's threads; ergo, they are yours. You're running Eclipse, > you're responsible for the chaos it creates.
... but AFAIK only the non-daemon threads are problematic. The JVM shouldn't care about existing daemon threads when trying to shut down. So the only one in the list to care about is "Worker-JM". Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
