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=3 , 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="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.
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
