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: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4DA44501.5000303@ice-sa.com>
Date: Tue, 12 Apr 2011 14:26:41 +0200
From: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Simple Tomcat monitoring ?
References: <4DA42761.1020403@ice-sa.com>
 <BANLkTikUmukAY7y9_H0nBcNYaZO1ofbN9w@mail.gmail.com>
In-Reply-To: <BANLkTikUmukAY7y9_H0nBcNYaZO1ofbN9w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Francis GALIEGUE wrote:
> On Tue, Apr 12, 2011 at 12:20, André Warnier <aw@ice-sa.com> wrote:
> [...]
>> Considering all the above, which would be the easiest/quickest way of
>> starting to figure out what this tomcat is doing, and where the
>> system/application bottleneck might be ?
>>
> 
> We have the following tools, all very easy to setup and run:
> 
> * SNMP monitoring of the JVM (allows to see the amount of memory
> consumed, the number of threads, and others - the MIB is well
> defined);
> * a shell script sending the results of a kill -3 on the JVM (a thread dump);
> * a script which triggers when a java.lang.OutOfMemoryError is thrown.
> 
> If you are interested in any of it, I can tell you how we do it.
> 
> And, considering that your server has 12 GB RAM, you could indeed do
> with a little more heap space!
> 

Thanks. I think I'll accept your offer of details.

I don't think that OOM is a problem, but the first 2 would be a good start.

About SNMP monitoring : I already have a "munin agent" installed on that system, and a 
munin server collecting stuff like overall cpu and memory usage.
To your knowledge, does there exist a way to collect this JVM SNMP information via a munin 
plugin ?


About the script doing a kill -3 : where does the thread dump go, when you do that ? and 
how does the script know which PID is Tomcat ?

On that system, the tomcat processes look like this :

# ps -ef | grep java
root     20997     1  0 12:18 ?        00:00:00 /usr/bin/jsvc -user tomcat55 -cp 
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar -outfile SYSLOG 
-errfile SYSLOG -pidfile /var/run/tomcat5.5.pid -Djava.awt.headless=true -Xms128M -Xmx128M 
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed 
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5 
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties 
org.apache.catalina.startup.Bootstrap
root     20998 20997  0 12:18 ?        00:00:00 /usr/bin/jsvc -user tomcat55 -cp 
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar -outfile SYSLOG 
-errfile SYSLOG -pidfile /var/run/tomcat5.5.pid -Djava.awt.headless=true -Xms128M -Xmx128M 
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed 
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5 
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties 
org.apache.catalina.startup.Bootstrap
tomcat55 20999 20997  0 12:18 ?        00:00:04 /usr/bin/jsvc -user tomcat55 -cp 
/usr/share/java/commons-daemon.jar:/usr/share/tomcat5.5/bin/bootstrap.jar -outfile SYSLOG 
-errfile SYSLOG -pidfile /var/run/tomcat5.5.pid -Djava.awt.headless=true -Xms128M -Xmx128M 
-Djava.endorsed.dirs=/usr/share/tomcat5.5/common/endorsed 
-Dcatalina.base=/var/lib/tomcat5.5 -Dcatalina.home=/usr/share/tomcat5.5 
-Djava.io.tmpdir=/var/lib/tomcat5.5/temp 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.util.logging.config.file=/var/lib/tomcat5.5/conf/logging.properties 
org.apache.catalina.startup.Bootstrap
vogon2:~#

So there are 3 Tomcat-related processes, all running under jsvc.  I am not quite sure 
which one does what.


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