Jeffrey Janner wrote:
Adam -
If you have the physical memory for it, you might want to look into breaking
your sites into multiple Tomcat instances (see RUNNING.TXT in the install
directory). At a minimum, you won't have to restart all sites just because one
becomes a memory hog. Plus it
Hello
Maybe Tcat from mulesoft is something to look into
regards
Milko
Adam Lipscombe
adam.lipscombe@g
Hi,
See interleaved.
On 3 February 2011 09:57, Adam Lipscombe adam.lipsco...@gmail.com 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
On Thu, 03 Feb 2011 09:57:59 +, Adam Lipscombe
adam.lipsco...@gmail.com wrote:
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
There is clearly only one solution ;-)
http://moskito.anotheria.net
Ok, advertisement aside, there are multiple, but moskito provides most
information of all the available tools.
Feel free to ask offlist too.
regards
Leon
On Thu, Feb 3, 2011 at 10:57 AM, Adam Lipscombe
adam.lipsco...@gmail.com
n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 3 Feb 2011 11:40:08 +0100
Subject: Re: Monitoring production tomcat
From: rosenberg.l
On 03/02/2011 09:57, Adam Lipscombe wrote:
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,
