Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Question about Tomcat memory leaks
Date: Sat, 12 Apr 2008 09:27:10 +0200
Message-ID: 
 <405A8DA9BECB2940B758D3521DFCF6C03F7FC0@sparus-exchange.ad.sparus.fr>
In-Reply-To: <4OKwfYS7SnPYy3kd0ToShdXoT6TW0K0IZiwLLfOTW6b@akmail>
thread-topic: Question about Tomcat memory leaks
Thread-Index: AcibziHyEPQbwDhATv2Spk4xKIHxPgAnsLcA
References: <47EE22F7.9080804@kippdata.de> <47EE5F3E.1050007@apache.org>
 <47EEF816.8020509@apache.org>
 <4OKwfYS7SnPYy3kd0ToShdXoT6TW0K0IZiwLLfOTW6b@akmail>
From: "Christophe Pierret" <cpierret@sparus-software.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>

Hi Guenter,
You could have a look at:
http://wiki.apache.org/tomcat/FAQ/Memory
But since you describe "server" memory exhaustion, you should use =
Windows perfmon tool to log process memory (see  HOW TO: Create and =
Configure Performance Monitor Trace Logs, =
http://support.microsoft.com/?kbid=3D302552 ) and determine which =
process is leaking.  If this is tomcat, then start by reducing -Xmx =
option to a level that the server can handle (and not crash).
And finally, use the very good suggestions of others to use a java =
memory profiler.

Regards,
Christophe

-----Message d'origine-----
De=A0: Guenter Knauf [mailto:fuankg@apache.org]=20
Envoy=E9=A0: vendredi 11 avril 2008 14:18
=C0=A0: dev@tomcat.apache.org
Objet=A0: Question about Tomcat memory leaks

Hi all,
I've a prob with a Tomcat application.
This is an app which was bought by a customer which I work for.
The app runs on a plain WinXP box with nothing else installed on it but =
only the Tomcat servive + MySQL server. The app is used through the =
standalone http connector; Tomcat version is 5.5.25.
Now since few days the box tends to crash with all memory exhausted...
I cant tell at the moment if any component of the involved software =
packages was updated recently.
Now my question is: can someone give me some hints how I can observe the =
memory consumption of Tomcat to see if there might be a leak either in =
Tomcat self (saw some BZ, and ChangeLog entries that something was fixed =
with 5.5.26), or also with their app?

thanks in advance for any suggestions!

greets, Guen.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org