tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Delle Grazie <>
Subject Re: Monitoring production tomcat
Date Thu, 03 Feb 2011 10:22:19 GMT

See interleaved.

On 3 February 2011 09:57, Adam Lipscombe <> wrote:
> Folks
> We have a several production servers, each of which runs 1 instance of
> tomcat. Within each instance of tomcat there are approximately 10
> virtual websites. Each virtual website runs a copy of our web app.
> Therefore each server hosts @ 10 instances of our web app
> On a couple of the servers we are having problems with tomcat running
> out of memory and sometimes dropping the JDBC link to the MYSQL database
> etc.
> We usually restart tomcat, which of course cures the issues. However doing
> do affects every virtual site and therefore is not ideal from our customer's
> perspective.
> We have been looking at this problem for some time, however it is very
> difficult to determine what is causing these problems. Very likely something
> in out webapp.
> What would help is some kind of management or monitoring facility
> that allows us to see which virtual site is getting into trouble.
> Ideally it should give enough information to help us track down what is
> causing the issue. Memory usage per site, thread view etc.
> Can anyone recommend anything that can do this? Commercial or free?

You're going to need to do some research as not all of the suggestions
below will be suitable for your
specific setup.

The ones I know about are:
Standard JVM monitoring (SNMP/JMX):

Standard JMX Tomcat monitoring: (uses above)

Ones that integrate with the Application or Tomcat (open-source): (replaces lambda probe which is
integrated into tcat server from mulesoft)


That's all I've got right now.

> Many thanks - Adam

Best Regards,

Brett Delle Grazie

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message