> From: Wayne Pope [mailto:waynemailingli...@gmail.com] > Subject: Very slow shutdown - 3 mins > > I've done a thread dump, but as far as I can tell all > looks ok.
Not to me. You have numerous threads apparently spawned by a webapp that are still sitting around. Whatever webapp is responsible for them needs to implement a ServletContextListener to terminate those threads when the webapp is stopped. Tomcat knows nothing about them, so it can't do it. Some of the threads of interest that do not belong to Tomcat or the JVM: > "pool-1-thread-10" prio=3 tid=0x085b8800 nid=0x38 > "pool-1-thread-9" prio=3 tid=0x08e0b400 nid=0x37 > "pool-1-thread-8" prio=3 tid=0x09550c00 nid=0x36 > "pool-1-thread-7" prio=3 tid=0x08e74400 nid=0x35 > "pool-1-thread-6" prio=3 tid=0x08739000 nid=0x34 > "pool-1-thread-5" prio=3 tid=0x08b5e400 nid=0x32 > "pool-1-thread-4" prio=3 tid=0x08681400 nid=0x31 > "pool-1-thread-3" prio=3 tid=0x08b5f800 nid=0x2f > "pool-1-thread-2" prio=3 tid=0x0839f800 nid=0x2d > "pool-1-thread-1" prio=3 tid=0x087f6c00 nid=0x2a > "pool-3-thread-1" prio=3 tid=0x083fe400 nid=0x29 The above appear to be associated with some outbound HTTP call mechanism. Since they're not daemon threads, they won't go away nicely until someone tells them to (or Tomcat gets tired of waiting). > "MultiThreadedHttpConnectionManager cleanup" daemon prio=3 tid=0x0824a400 > nid=0x30 The manager for the above pooled threads. > "MySQL Statement Cancellation Timer" daemon prio=3 tid=0x08498400 nid=0x18 Again, not a thread Tomcat creates, but at least it's a daemon. - 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
