Mott Leroy wrote:
Mladen Turk wrote:
Yes, use the 'Advanced worker directives'
http://tomcat.apache.org/connectors-doc/config/workers.html
The connect_timeout, prepost_timeout and reply_timeout are meant to
be used with hanged or very busy backend (Tomcat) servers.
I'm having trouble understanding the difference between a
prepost_timeout and a connect_timeout ... both seem to happen before a
request is forwarded.
1. connect_timeout happens when the physical connection between
mod_jk and Tomcat is established. The Tomcat might accept the
physical connections, but might refuse to serve it.
2. prepost_timeout happens before each request on already opened
connection, and is meant to be used to solve the hanged Tomcats,
and to replace the 'socket_timeout' functionality on platforms
that does not have a full BSD socket implementation (Solaris).
Are these pings happening for every request
(doubling the load?) ?
Yes, they happen on every request, but the packet size is 8 bytes, so
the load increase is negligible compared with robustness.
Also, what happens to the request if reply_timeout is exceeded? Does the
request get dropped? Or is it somehow retried on another server in the
cluster? [not saying it should .. it's ambiguous what should happen]
It depends on the 'recovery_options' for a worker.
By default the request will be forwarded to another worker in lb.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
