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 (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Question about the "compress" setting MIME-Version: 1.0
Date: Sat, 9 Sep 2006 09:10:57 -0400
Message-ID: <038EB0A80FC11643BBCC136CE66BD5D55C2C22@EXMAILNAS1.amr.smtf.ds>
Thread-Topic: Question about the "compress" setting MIME-Version: 1.0
thread-index: AcbT0XhNV2bATiZPQ1yG2aT5/+dkwgAPK0RA
From: "Derrick Koes" <Derrick_Koes@skillsoft.com>
To: "Tomcat Users List" <users@tomcat.apache.org>


Sounds like a bandwidth/throughput problem if you are concerned with the
connector compression attribute.  You may want to try some performance
tuning with the throughput garbage collector.

Assuming your problem is an OutOfMemory Error and at least Java 1.4.1,
try the following VM settings
-Xmn=3D1024m
-Xmx=3D1024m
-XX:+AggressiveHeap
-XX:+UseParallelGC
-XX:MaxPermSize=3D128m

Below is reference documentation.

http://java.sun.com/docs/hotspot/gc1.4.2/
http://java.sun.com/j2se/1.4.2/1.4.2_whitepaper.html

If you still have memory problems, try a memory profiler like Jprofiler
to detect memory leaks as well as CPU issues.
http://www.ej-technologies.com/products/jprofiler/overview.html

It would be helpful if you posted any errors in the log files when you
incur the issue.

-----Original Message-----
From: JMonstad@gkservices.com [mailto:JMonstad@gkservices.com]=20
Sent: Saturday, September 09, 2006 1:33 AM
To: users@tomcat.apache.org
Subject: Question about the "compress" setting MIME-Version: 1.0

We currently have an app in prod using the original servlet filer
described at
http://www.onjava.com/pub/a/onjava/2003/11/19/filters.html?page=3D3  , =
and
I know  from the comments to the article in the link that there may be
some issues with it. My question is; how does the built-in tomcat
implementation, which is activated by the compress=3D"true" attribute on
the default http1.1 connector improve on the servlet filter mentioned
above. For context, I should mention that  we're running on Windows 2003
server, sp1 using Apache Tomcat/5.0.28 on on dual Intel Xeon processor
with 4Gb of RAM.=20
Under various memory settings ranging from giving the heap from any
interval of  800 - 1500 MB of heap space, the Tomcat server will die
more or less silently under even moderate load (heavy load kills it
almost immediately).
Any help would be appreciated, and as I've mentioned (username jmonstad)
on the IRC channel, I may be willing to entertain engagements from local
to Minneapolis, US gurus for $'s=20

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