t: Re: [us...@httpd] RE: mod_proxy_balancer back end status check
On 9 March 2010 23:01, Edward Quick wrote:
> Further testing showed this succeeded when the server was busy. The balancer
> marked the member's status as Err.
> However later after firing continuous requests, the
On 9 March 2010 23:01, Edward Quick wrote:
> Further testing showed this succeeded when the server was busy. The balancer
> marked the member's status as Err.
> However later after firing continuous requests, the backend ran out of
> memory, causing it to return a 500, and then the balancer mark
:edward.qu...@igindex.co.uk]
Sent: 09 March 2010 22:08
To: users@httpd.apache.org
Subject: RE: [us...@httpd] RE: mod_proxy_balancer back end status check
Thanks Phil,
That worked a treat.
BalancerMember ajp://localhost:8009 route=jvm001 redirect=jvm002 keepalive=On
ping=1 BalancerMember ajp://localhost:
2010 19:57
To: users@httpd.apache.org
Subject: Re: [us...@httpd] RE: mod_proxy_balancer back end status check
On 9 March 2010 17:47, Edward Quick wrote:
> Here's my configuration. After the 15 seconds timeout, the back end
> server (listening on port 8080 here) returns a 502 page. I
On 9 March 2010 17:47, Edward Quick wrote:
> Here’s my configuration. After the 15 seconds timeout, the back end server
> (listening on port 8080 here) returns a 502 page. Is there any
> configuration I can add to detect that beforehand, and get the balancer to
> redirect my request to the other
