... adding to previous post:
It also does not retry/fail over, in the following (more or less obvious
cases):
- there was a problem with the client (browser) connection
- we already started to send back parts of the response to the client,
typically the headers (depending on recovery_options; default:
retry/fail over)
- Internal JK error (not observed in practise yet)
- depending on recovery_options: if the backend received the request
(default: retry/fail over)
Regards,
Rainer
Dominik Pospisil wrote:
Indeed. It would be OK to return 503, for requests, that already have
been received by the first node, but not returned yet. New requests
That's the case. All errors I am getting are from requests which were allready
in processing by failing node. Why it is OK to return 503 for such requests?
Why after mod_jk detect failure does not redirect them to second node? I have
recovery_option attribute set to zero.
I am sorry for disturbing you with questins again, but it is really essential
for me to learn how mod_jk failover works in detail.
Thanks again,
Dominik
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
