On 14.07.2009 04:34, Madhuri Patwardhan wrote: Did you read the docs page about timeouts:
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html If you are very concerned about timeouts, use version 1.2.28, because it has an additional socket_connect_timeout. > connect_timeout and preprost_timeout what would be the typical > values? something like "5000" or less/more? I wouldn't choose less. The ping timeout usually shouldn't fire. By going to extremes, very small problems might lead to an unacceptable big reaction (taking a worker out of balancing, only because a ping took a second or so). Note, that in 1.2.28 there is an alternative unified way of setting the ping_timeout. > I also wonder if I specify prepost_timeout then it would mean now > each request would take that much additional time?Before serving > each request cping/cpong would be tried with timeout value of > prepost_timeout so that adds little delay to serving the request?? Yes, before each request it adds a little latency, but usually only very few milliseconds, because the ping processing is very simple. It adds roughly double the network latency between your Apache and Tomcat, which for a normal LAN will be a single digit millisecond number. I usually rate the improved stability higher than this additional resource use and latency. > Also, a typical value for recovery_options would be "3". ... or "7". Concerning reply timeout: Also set max_reply_timeouts. Don't push reply_timeouts to low. In 1.2.28 you can set a general reply_timeout and set more specific ones for individual URL patterns, e.g. if you have some URLs that you expect to respond very sow (report generation etc.). This is done using extensions. See http://tomcat.apache.org/connectors-doc/reference/uriworkermap.html#Rule%20extensions Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
