Christopher Schultz wrote:
Rainer Jung wrote:
2. Is is okay to have connection_pool_size=1 for my workers? The docs
suggest to me that it /must be/ set to 1 if I'm using prefork MPM.
OK, I see, that our wording is still not clear. What we try to tell the
users:
I think I get it. Basically, the best practice is to leave this setting
to the default (when using Apache httpd) unless there's some kind of
problem. Is that about it?
Yes. The only thing one can do is to decrease the value from the
default. For prefork, there is no useful value smaller than the default
"1", for worker there could be, but the implications of decreasing are
dificult to understand.
worker.worker3.connection_pool_timeout=60
OK. Maybe a little short. 600 (10 minutes) should be OK as well. It
would be good to adjust connectionTimeout in the Tomcat AJP connector to
the same value (multiplied by 1000, because it's milliseconds there). We
proudly present the new docs page
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html.
60 seconds ought to be enough for a localhost connection to pick up the
phone, no? If a web user has to wait 60 seconds, they're going to hit
RELOAD anyway.
This is not a reply timeout. This timeout means: if mod_jk detects a
backend connection, which was not used during the last XXX seconds, then
shut it down. mod_jk uses persistent backend connections, we don't want
to open a backend connection for each new request. But of course load is
increasing and decreasing, so if you have more backend connections than
you need for a long time, it would be OK, to shut them down (each
backend connections needs a separate thread inside tomcat, even if there
are no requests handled).
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
