RE: tomcat 6.0.18 doesn't fully shutdown
> From: nocturna_gr [mailto:kostaspa...@yahoo.gr] > Subject: Re: tomcat 6.0.18 doesn't fully shutdown > > this is a daemon thread... The thread of interest is this one: "DelayActionThread" prio=6 tid=0x237bd000 nid=0x368 waiting on condition [0x2490f000..0x2490fa14] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at com.lhs.ccb.common.DelayAction.run(DelayAction.java:200) Not a daemon, and not part of Tomcat. - 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
Re: tomcat 6.0.18 doesn't fully shutdown
Thanks for your answer Mark, i thought the same thing, but this is a daemon thread... it should cause any problems, isn't it so? markt-2 wrote: > > On 18/02/2010 10:16, nocturna_gr wrote: >> >> Hallo, >> i am running an application (Spring+Framework+Quartz) in tomcat 6.0.18 >> under >> Windows XP and JDK 1.6.0_16. When i shutdown tomcat (either script or >> SHUTDOWN via 8005 port), there are always some threads hanging. They are >> not >> related to the application, as far as i can see- although it problems >> with >> "Spring+Framework+Quartz". The thread stack follows; i can see some locks >> there... Does somebody have some advice? I am new in Tomcat (and threaded >> debugging) so any directions would be appreciated > > If you start a TimerThread you are expected to stop it. This is normally > done by cancelling whatever jobs you scheduled. > > Tomcat 6.0.25 will include code to automatically stop forgotten timer > threads but that is only a workaround. > > Mark > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://old.nabble.com/tomcat-6.0.18-doesn%27t-fully-shutdown-tp27636692p27638624.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 6.0.18 doesn't fully shutdown
Mark Thomas wrote: On 18/02/2010 10:16, nocturna_gr wrote: Hallo, i am running an application (Spring+Framework+Quartz) in tomcat 6.0.18 under Windows XP and JDK 1.6.0_16. When i shutdown tomcat (either script or SHUTDOWN via 8005 port), there are always some threads hanging. They are not related to the application, as far as i can see- although it problems with "Spring+Framework+Quartz". The thread stack follows; i can see some locks there... Does somebody have some advice? I am new in Tomcat (and threaded debugging) so any directions would be appreciated If you start a TimerThread you are expected to stop it. This is normally done by cancelling whatever jobs you scheduled. I sometimes run into shutdown problems as well, and I'm running as a windows service. Does this mean I need to cancel the timer itself, or just any jobs that are in progress that were started by the timer? D Tomcat 6.0.25 will include code to automatically stop forgotten timer threads but that is only a workaround. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 6.0.18 doesn't fully shutdown
On 18/02/2010 10:16, nocturna_gr wrote: > > Hallo, > i am running an application (Spring+Framework+Quartz) in tomcat 6.0.18 under > Windows XP and JDK 1.6.0_16. When i shutdown tomcat (either script or > SHUTDOWN via 8005 port), there are always some threads hanging. They are not > related to the application, as far as i can see- although it problems with > "Spring+Framework+Quartz". The thread stack follows; i can see some locks > there... Does somebody have some advice? I am new in Tomcat (and threaded > debugging) so any directions would be appreciated If you start a TimerThread you are expected to stop it. This is normally done by cancelling whatever jobs you scheduled. Tomcat 6.0.25 will include code to automatically stop forgotten timer threads but that is only a workaround. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat 6.0.18 doesn't fully shutdown
Hallo, i am running an application (Spring+Framework+Quartz) in tomcat 6.0.18 under Windows XP and JDK 1.6.0_16. When i shutdown tomcat (either script or SHUTDOWN via 8005 port), there are always some threads hanging. They are not related to the application, as far as i can see- although it problems with "Spring+Framework+Quartz". The thread stack follows; i can see some locks there... Does somebody have some advice? I am new in Tomcat (and threaded debugging) so any directions would be appreciated 2010-02-18 10:55:58 Full thread dump Java HotSpot(TM) Client VM (11.0-b16 mixed mode): "DestroyJavaVM" prio=6 tid=0x002b7c00 nid=0xf14 waiting on condition [0x..0x0090fd4c] java.lang.Thread.State: RUNNABLE "http-8080-1" daemon prio=6 tid=0x2331f000 nid=0x128 in Object.wait() [0x24dbf000..0x24dbfa94] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416) - locked <0x07851038> (a org.apache.tomcat.util.net.JIoEndpoint$Worker) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442) at java.lang.Thread.run(Thread.java:619) "http-8080-Acceptor-0" daemon prio=6 tid=0x2342d400 nid=0x77c waiting on condition [0x24d6f000..0x24d6fb14] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:302) at java.lang.Thread.run(Thread.java:619) "Timer-1" daemon prio=6 tid=0x23b4d000 nid=0xaf8 in Object.wait() [0x2495f000..0x2495fd94] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x076b6e20> (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:509) - locked <0x076b6e20> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:462) "DelayActionThread" prio=6 tid=0x237bd000 nid=0x368 waiting on condition [0x2490f000..0x2490fa14] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at com.lhs.ccb.common.DelayAction.run(DelayAction.java:200) "Low Memory Detector" daemon prio=6 tid=0x22c5f400 nid=0xbb8 runnable [0x..0x] java.lang.Thread.State: RUNNABLE "CompilerThread0" daemon prio=10 tid=0x22c5c400 nid=0x5f8 waiting on condition [0x..0x2300fa3c] java.lang.Thread.State: RUNNABLE "JDWP Command Reader" daemon prio=6 tid=0x22c4e800 nid=0xb2c runnable [0x..0x] java.lang.Thread.State: RUNNABLE "JDWP Event Helper Thread" daemon prio=6 tid=0x22c4cc00 nid=0x824 runnable [0x..0x] java.lang.Thread.State: RUNNABLE "JDWP Transport Listener: dt_socket" daemon prio=6 tid=0x22c49400 nid=0x12c runnable [0x..0x22f1fa7c] java.lang.Thread.State: RUNNABLE "Attach Listener" daemon prio=10 tid=0x22c3e000 nid=0x538 runnable [0x..0x] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=10 tid=0x22c3cc00 nid=0xee0 runnable [0x..0x] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=8 tid=0x22c2d400 nid=0xc58 in Object.wait() [0x22d9f000..0x22d9fc94] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116) - locked <0x03d43c30> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) "Reference Handler" daemon prio=10 tid=0x22c28800 nid=0x1f4 in Object.wait() [0x22d4f000..0x22d4fd14] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked <0x03d43c50> (a java.lang.ref.Reference$Lock) "VM Thread" prio=10 tid=0x22c25400 nid=0x20c runnable "VM Periodic Task Thread" prio=10 tid=0x22c60c00 nid=0x6c0 waiting on condition JNI global references: 14468 -- View this message in context: http://old.nabble.com/tomcat-6.0.18-doesn%27t-fully-shutdown-tp27636692p27636692.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
