Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: RE: Tomcat STILL freezing - time to look at another app server?
Date: Fri, 30 May 2003 11:38:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <C19D2E05B25FA94E943431666541E5B71C8C93@server01.hh.uptime.de>
content-class: urn:content-classes:message
Thread-Topic: Tomcat STILL freezing - time to look at another app server?
Thread-Index: AcMlMatClxqRBQ7cTReC8Nf3XS1AdgAAIkkwAFblM5A=
From: "Ralph Einfeldt" <ralph.einfeldt@uptime-isc.de>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>

In this case I don't completly agree with you.

Through the implementation of a servlet container you=20
can incluence the behaviour of the gc. It depends on how=20
many objects are created by the different containers=20
to complete the same task and how the lifecycle of the=20
created objects is. Given that, the same gc parameters=20
can work good with one container, and can perform bad on=20
another.

Note that I'm not suggesting that tomcat performs better=20
or worse than other containers, just that it is possible=20
that there are differences.

> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Wednesday, May 28, 2003 6:01 PM
> To: Tomcat Users List
> Subject: RE: Tomcat STILL freezing - time to look at another=20
> app server?
>=20
> GC behavior is not tomcat-specific.  It's the JVM that's doing the GC,
> and if you have a stop-the-world full GC algorithm triggered, then
> everything in the JVM will stop.  Again, not related to=20
> tomcat.  Bad GC tuning will bite you on every server.
>=20

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