Hi, Lindsay,
Sorry for my ignorance, but seeing that you were trying to locate the
thread using "PID", I think perhaps it's wrong. I have the same
experience identifying such a CPU utilization issue on a Debian box
using a 2.6.x version kernel. I cannot recall whether on a 2.4.x
kernal linux box y
Thank you to the several people who made suggestions, either on the list
or by direct email!
I think I have solved the problem by simply using the -server option to
java when starting tomcat. By default tomcat uses the default VM, which
for Sun JDK1.5 is the client VM. By default the client
> From: Lindsay Patten [mailto:[EMAIL PROTECTED]
> Subject: Re: 100% cpu usage by "VM Thread" in tomcat
>
> I need to figure out how to reproduce the situation out of
> the production server to see how I can use it...
For an initial check, set -Dcom.sun.management
Looking at the cpu times, top says that pid 324 has used over 900
minutes of cpu time, none of the other tomcat threads have used more
than 9 minutes. When the system is grinding it is pid 324 that is
listed as 97% of cpu with no other java threads on screen. The problem
may be caused by some
> From: Lindsay Patten [mailto:[EMAIL PROTECTED]
> Subject: 100% cpu usage by "VM Thread" in tomcat
>
> Expecting to find that I had some error in my webapp I did a
> few thread dumps, but assuming that nid in the thread dump
> corresponds to pid from ps I found that the process that was
> spinn
On 9/21/07, Lindsay Patten <[EMAIL PROTECTED]> wrote:
[ ...stuff elided...]
>
> If I look at the system status using the Tomcat manager webapp there are
> often requests listed with ridiculously large values in the Time column,
> several hundred seconds for jsp pages that only take a fraction of a
