Hi Dominik,
Eventually, after killing 1st node, and after returning couple of "503
Service Temporarily Unavailable" exceptions, mod_jk finally recheck 2nd
node status, reroute requests to 2nd node and resumes correct operation.
Still, I it is not clear to me, why I am getting 503 exceptions. I believe
that when there is one or more servers up and ready to serve request, this
should not happend. Why the requests are not immidiatelly rerouted to second
node, which is couple of minutes up and running (in ERR/REC state) ?
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
should not run into errors though. But: it also depends on the type of
node failure, more precisely on its exact behaviour on the network. To
make problem detection more robust, you can especially enable connect
and prepost timeout. See
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
I can imagine, that with your default configuration (timeouts disabled)
you might run into long TCP timeouts and e.g. the httpd default timeout
of 5 minutes or an overload situation because to many requests where
waiting to long results in the error.
If cping/cpong doesn't help: To find out the reason for the 503, you can
have a look at the JK log file. Look for log lines with "[error]", only
those indicate final errors. To find out about more detailed reasons of
those errors, it might help to look at the associated "[info]" log
lines. Associated means shortly before in time and having the same
process and thread id "[pid:tid]".
Thanks,
Dominik
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]
