Dear Leon,
Oh, don't be so dramatic. There is a whole world out there of smaller
companies that have one or two Tomcat servers in production,
running on the
cheapest shared server environment they could find. This product
targets
companies that have two or three developers, one of whom has
Dear Chris,
I am setting up a monitoring system for Tomcat servers and I am
looking
for hard limits in Tomcat servers in general.
I found a few so far: file descriptors, memory pools (ok, these are
jdk
limits) and thread pools.
Are there any other hard limits that I can run into?
I
I think the question you wanna ask yourself first is,
do you want to monitor tomcat or do you want to monitor your application?
regards
Leon
On Wed, Nov 19, 2008 at 3:18 PM, Kees Jan Koster [EMAIL PROTECTED] wrote:
Dear Chris,
I am setting up a monitoring system for Tomcat servers and I am
Dear Leon,
I think the question you wanna ask yourself first is,
do you want to monitor tomcat or do you want to monitor your
application?
I want to monitor Tomcat, not the application. I'm using the
information to improve the Tomcat monitoring on Java-monitor.com.
Currently you can see
is there a demo available on the java-monitor.com? sofar i only find a
php forum :-)
Leon
On Wed, Nov 19, 2008 at 3:31 PM, Kees Jan Koster [EMAIL PROTECTED] wrote:
Dear Leon,
I think the question you wanna ask yourself first is,
do you want to monitor tomcat or do you want to monitor your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keen Jan,
Kees Jan Koster wrote:
Ah, sorry for the confusion. I should have asked for limits that are
hard at run-time. Thread pool sizes may be editable, but they are fixed
once Tomcat runs.
Gotcha. Hard runtime limits makes a whole lot more
Dear Leon,
is there a demo available on the java-monitor.com? sofar i only find a
php forum :-)
The forum has the monitoring tool built-in. A bit weird at forst, but
it makes it really simple to post questions, as you can just post
graphs from the tool right on the forum. No need to make
Dear Chris,
Ah, sorry for the confusion. I should have asked for limits that are
hard at run-time. Thread pool sizes may be editable, but they are
fixed
once Tomcat runs.
Gotcha. Hard runtime limits makes a whole lot more sense. Sorry for
not
jumping to that obvious conclusion. I wasn't
well, downloaded, installed, started, klicked, ... deleted...
you should announce that your war is SENDING DATA to the central
server in LARGE letters :-)
which users are you targeting? No one i know (and i'm in the webapp
business for about 10 years) will ever going to use this stuff, since
its
.
Regards,
-Tony
--- On Wed, 11/19/08, Leon Rosenberg [EMAIL PROTECTED] wrote:
From: Leon Rosenberg [EMAIL PROTECTED]
Subject: Re: Hard limits in Tomcat?
To: Tomcat Users List users@tomcat.apache.org
Date: Wednesday, November 19, 2008, 7:23 AM
I think the question you wanna ask yourself first
Dear Leon,
well, downloaded, installed, started, klicked, ... deleted...
you should announce that your war is SENDING DATA to the central
server in LARGE letters :-)
which users are you targeting? No one i know (and i'm in the webapp
business for about 10 years) will ever going to use this
Hello Kees Jan,
On Wed, Nov 19, 2008 at 8:25 PM, Kees Jan Koster [EMAIL PROTECTED] wrote:
Dear Leon,
Oh, don't be so dramatic. There is a whole world out there of smaller
companies that have one or two Tomcat servers in production, running on the
cheapest shared server environment they could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kees Jan,
Kees Jan Koster wrote:
I am setting up a monitoring system for Tomcat servers and I am looking
for hard limits in Tomcat servers in general.
I found a few so far: file descriptors, memory pools (ok, these are jdk
limits) and thread
13 matches
Mail list logo
