> That sounds like you looked at ps or similar output, not a thread dump. Take
> an actual JVM thread dump and see where the worker threads are during the
> busy periods.
Wrong, to identify the thread in question I looked with Sysinternals Process
Explorer which thread ID caused the 100% CPU.
> From: Michael Südkamp [mailto:michael.suedk...@docware.de]
> Subject: AW: server status reports long request times
> We looked at thread dumps several times. The CPU charge was always
> reported for the "VM Thread" and we didn't know how this information
> coul
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 20. Juli 2011 11:06
An: Tomcat Users List
Betreff: Re: server status reports long request times
Hello Andre
"a certain client" related to the entries in the "client" colu
On 20/07/2011 09:15, Michael Südkamp wrote:
> Hello,
>
> From time to time we have customers experiencing Tomcat going to
> 100% CPU. One customer sent us the output from the server status
> page from the Tomcat 6.0.32 Manager web-app. This page reports a lot
> of HTTP connector requests belongi
Michael Südkamp wrote:
Hello,
From time to time we have customers experiencing Tomcat going to 100% CPU.
One customer sent us the output from the server status page from the Tomcat 6.0.32 Manager
web-app.
This page reports a lot of HTTP connector requests belonging to a certain client
can
Hello,
>From time to time we have customers experiencing Tomcat going to 100% CPU.
>One customer sent us the output from the server status page from the Tomcat
>6.0.32 Manager web-app. This page reports a lot of HTTP connector requests
>belonging to a certain client with stage value "S" and "
