Hi Sean,
On 20.04.2010 08:04, Sean GAO wrote:
According to online documentation
(http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html):
Long Garbage Collection pauses on the backend do not make a good fit
with some timeouts. Try to optimise your Java memory and GC settings.
Hi Rainer,
Thanks for your informative and thoughtful reply.
Yes, we are definitely going with CMS. It's a product environment so
we have to be careful with whatever we plan to do. By tweaking
reply_timeout, be it hard or soft, we were actually circumventing the
problem rather than facing it.
According to online documentation
(http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html):
Long Garbage Collection pauses on the backend do not make a good fit
with some timeouts. Try to optimise your Java memory and GC settings.
So if JVM tuning doesn't help, what else
Hi,
We are running apache 2.2.4 and tomcat 5.5.28 with mod_jk 1.2.28. 3
tomcat instances.
Referring to http://tomcat.apache.org/connectors-doc/reference/workers.html
, we came up with a workers.properties file like this:
worker.list=balancer
worker.maintain=30
#tomcat01
