Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of jks@selectacast.net
 designates 199.107.233.208 as permitted sender)
Message-ID: <419BD33C.3040806@selectacast.net>
Date: Wed, 17 Nov 2004 17:39:56 -0500
From: Joseph Shraibman <jks@selectacast.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Analysing dead threads
References: <E1CThC0-0003xW-7o@mx.sh-solutions.de>
In-Reply-To: <E1CThC0-0003xW-7o@mx.sh-solutions.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org