check if ajp port is already in use or not.
If hte port is already in use tomcat internally increments the port by one
and starts listening to that port for requests.
In this scenario apache won't be able to forward your requests to respective
node.
kashif_tomcat wrote:
>
> Hi All,
>
> i am doi
I did the same trick.
When my back-end server is down i throw HTTP 503 servlet error from
respective worker node.
The error is shown to the user only for the first time. But after refreshing
the browser the request is redirected to some other working node (even if
the load on the node is more than
