It would appear from this post:
http://apache-http-server.18135.x6.nabble.com/Help-regarding-mod-proxy-balancer-failover-and-failonstatus-td4998183.html
that failover (with no error message) will only occur when a connection to
the instance cannot be made. I suppose as the instance was shutting d
I did see the ping parameter for the Balancemember element could be used to
test the connection - should we be using this? I'm worried about more load
on the tomcat instances though using this.
On Wed, Apr 20, 2016 at 3:07 PM, Wayne W
wrote:
> Hi Jim,
>
> I did't know that - is there any documen
Hi Jim,
I did't know that - is there any documentation around this? what should I
search for?
So are you saying what I'm experiencing is normal?
On Wed, Apr 20, 2016 at 2:05 PM, Jim Jagielski wrote:
> Upgrading to 2.4.20 allow you to disable the one node dynamically
> on the httpd side and the
Upgrading to 2.4.20 allow you to disable the one node dynamically
on the httpd side and then bring down the node.
> On Apr 20, 2016, at 8:10 AM, Wayne W wrote:
>
> Hi,
>
> I'm seeing that with Apache 2.4.12 on Solaris when setup with mod_proxy to 2
> tomcat instances when we bring down 1 node f
Hi,
I'm seeing that with Apache 2.4.12 on Solaris when setup with mod_proxy to
2 tomcat instances when we bring down 1 node for maintenance the first
client to try and access that node gets a Internal Server Error. Any
requests after that (and for other sessions) are balanced correctly onto
the ot
