Re: Analysing dead threads
Is this a redhat 9 box by any chance? Steffen Heil wrote: Hi I have a situation, where a lot of threads seem to stop working right in my servlet. From debug output, I know they entered the servlet but never leave it. My problem is that this never occurs on our development system, but only on the production system. I need to stop tomcat end even do a killall -9 java to get everything to stop. Then I restart tomcat. But I don't know what happened. I know there is a way to kill the JVM, so that I see the stack trace of kill threads. How can I do it? (Is there another way to see what those threads are waiting for?) Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Analysing dead threads
Hi Stefan, You might want to try kill -3 processid Depending on your JVM you may find a stacktrace in STDERR (STDIO?) or in a seperate file in the directory where you started the JVM Depending on the version of Tomcat you are running, you may also want to have a look at the manager application: http://www.myhost.com/manager/status Regards Andrew Steffen Heil wrote: Hi I have a situation, where a lot of threads seem to stop working right in my servlet. From debug output, I know they entered the servlet but never leave it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Analysing dead threads
kill -SIGHUP or kill -3 should dump a stack trace into catalina.out. A profiler should also tell you what the threads are up to. Ta Matt -Original Message- From: Steffen Heil [mailto:[EMAIL PROTECTED] Sent: 15 November 2004 13:42 To: 'Tomcat Users List' Subject: Analysing dead threads Hi I have a situation, where a lot of threads seem to stop working right in my servlet. From debug output, I know they entered the servlet but never leave it. My problem is that this never occurs on our development system, but only on the production system. I need to stop tomcat end even do a killall -9 java to get everything to stop. Then I restart tomcat. But I don't know what happened. I know there is a way to kill the JVM, so that I see the stack trace of kill threads. How can I do it? (Is there another way to see what those threads are waiting for?) Regards, Steffen Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Analysing dead threads
just for clarification. Do you mean zombie threads? Threads that are not reachable, but still running. My advice would be to download a profiler and figure out the cause. peter On Mon, 15 Nov 2004 14:42:14 +0100, Steffen Heil [EMAIL PROTECTED] wrote: Hi I have a situation, where a lot of threads seem to stop working right in my servlet. From debug output, I know they entered the servlet but never leave it. My problem is that this never occurs on our development system, but only on the production system. I need to stop tomcat end even do a killall -9 java to get everything to stop. Then I restart tomcat. But I don't know what happened. I know there is a way to kill the JVM, so that I see the stack trace of kill threads. How can I do it? (Is there another way to see what those threads are waiting for?) Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Analysing dead threads
Hi Peter, A profiler may cause more trouble than help if you try this on a heavily loaded production box. It might be easiest if he first looks at the 'manager' application that comes with tomcat 5. Regards Andrew Peter Lin wrote: just for clarification. Do you mean zombie threads? Threads that are not reachable, but still running. My advice would be to download a profiler and figure out the cause. peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
