Re: Windows Thread dump issue
2010/1/20 Jeffrey Janner jeffrey.jan...@polydyne.com: Is there a version where the Tomcat Monitor (Tomcat5w.exe) thread dump option doesn't work and one where it's been fixed? I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and Tomcat 5.5.27. When I right-click on the Tomcat monitor in the system tray and select Thread Dump, nothing appears to happen. I cannot find any new file, and the jakarta-service-xxx.log file is still at zero. Look in stdout_.log. I don't have 5.5 installed at the moment, but in 6.0 it is there. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Windows Thread dump issue
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Subject: Re: Windows Thread dump issue Look in stdout_.log. I don't have 5.5 installed at the moment, but in 6.0 it is there. Not for me - it's in jakarta_service_MMdd.log, in both 5.5 and 6.0. - 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: Windows Thread dump issue
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Subject: Windows Thread dump issue I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and Tomcat 5.5.27. I just tried it with Vista 64 using JDK 1.6.0_14, running both Tomcat 5.5.27 and 6.0.20. When I right-click on the Tomcat monitor in the system tray and select Thread Dump, nothing appears to happen. I cannot find any new file, and the jakarta-service-xxx.log file is still at zero. The size in Explorer doesn't update unless you refresh the window. The trace is there for me, on both levels. Open the file in an editor and take a look at it. - 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: Windows Thread dump issue
Sorry I wasn't clear. The file is empty. -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Wednesday, January 20, 2010 10:44 AM To: Tomcat Users List Subject: RE: Windows Thread dump issue From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Subject: Windows Thread dump issue I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and Tomcat 5.5.27. I just tried it with Vista 64 using JDK 1.6.0_14, running both Tomcat 5.5.27 and 6.0.20. When I right-click on the Tomcat monitor in the system tray and select Thread Dump, nothing appears to happen. I cannot find any new file, and the jakarta-service-xxx.log file is still at zero. The size in Explorer doesn't update unless you refresh the window. The trace is there for me, on both levels. Open the file in an editor and take a look at it. - 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 *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Windows Thread dump issue
Thanks Konstantin. That is where it was. Now I have something to document for the ops to run when the app hangs again. -Original Message- From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Sent: Wednesday, January 20, 2010 10:20 AM To: Tomcat Users List Subject: Re: Windows Thread dump issue 2010/1/20 Jeffrey Janner jeffrey.jan...@polydyne.com: Is there a version where the Tomcat Monitor (Tomcat5w.exe) thread dump option doesn't work and one where it's been fixed? I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and Tomcat 5.5.27. When I right-click on the Tomcat monitor in the system tray and select Thread Dump, nothing appears to happen. I cannot find any new file, and the jakarta-service-xxx.log file is still at zero. Look in stdout_.log. I don't have 5.5 installed at the moment, but in 6.0 it is there. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Windows Thread dump issue
2010/1/20 Caldarale, Charles R chuck.caldar...@unisys.com: From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Subject: Re: Windows Thread dump issue Look in stdout_.log. I don't have 5.5 installed at the moment, but in 6.0 it is there. Not for me - it's in jakarta_service_MMdd.log, in both 5.5 and 6.0. - Chuck 2010/1/20 Caldarale, Charles R chuck.caldar...@unisys.com: From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Subject: Windows Thread dump issue I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and Tomcat 5.5.27. I just tried it with Vista 64 using JDK 1.6.0_14, running both Tomcat 5.5.27 and 6.0.20. With 6.0.20 it ends up in jakarta_service_20100120.log, the service runner version there is 2.0.4. With 6.0.24 RC it ends up in stdout_20100120.log, the service runner version there is 2.0.6. Both on the same PC with JRE 6u17 and WinXP 32-bit. From a quick look at the procrun sources svn history, I do not see any specific commit that might have caused this change. And from last Jeffrey's reply below it looks like it can end up in either file. 2010/1/20 Jeffrey Janner jeffrey.jan...@polydyne.com: Thanks Konstantin. That is where it was. Now I have something to document for the ops to run when the app hangs again. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
