Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: 100% cpu usage by "VM Thread" in tomcat
Date: Fri, 21 Sep 2007 15:30:28 -0500
Message-ID: 
 <AEF3D568DD1D9E428048C592AA164597064D00CE@USRV-EXCH4.na.uis.unisys.com>
In-Reply-To: <46F42854.8000905@netscape.net>
Thread-Topic: 100% cpu usage by "VM Thread" in tomcat
Thread-Index: Acf8jX4AamNkpjnxQfe1GD7TkosqVgAAFU8w
References: <46F3FB48.1070101@netscape.net>
 <AEF3D568DD1D9E428048C592AA164597064CFFE0@USRV-EXCH4.na.uis.unisys.com>
 <46F42854.8000905@netscape.net>
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

> From: Lindsay Patten [mailto:BLindsayPatten@netscape.net]=20
> Subject: Re: 100% cpu usage by "VM Thread" in tomcat
>=20
> I need to figure out how to reproduce the situation out of=20
> the production server to see how I can use it...

For an initial check, set -Dcom.sun.management.jmxremote for the Tomcat
startup, and run JConsole when you see the problem.  (You could probably
run this all the time; it won't consume much in the way of CPU
resources.)  This will at least let you see if the heap is full and if
any long-running GCs occur.

 - 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org