https://issues.apache.org/bugzilla/show_bug.cgi?id=48939

Daniel Ruggeri <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |NeedsReleaseNote,
                   |                            |PatchAvailable

--- Comment #4 from Daniel Ruggeri <[email protected]> 2010-03-19 18:43:51 
UTC ---
Final patch added and functionality has been tested as follows:

<Proxy balancer://App_cluster>
   BalancerMember http://127.0.0.1:8001 route=1
   BalancerMember http://127.0.0.1:8002 route=2
   ProxySet lbmethod=byrequests stickysession=App_STICKY nofailover=Off
erroronstatus=500,502
</Proxy>

127.0.0.1 is answered by an Apache instance with valid CGI script and buggy CGI
script (causing 500).

Continuous hits to valid script:
   [1]http://127.0.0.1:8001 1                1      0   Ok     20      6.9K
3.1K
   [2]http://127.0.0.1:8002 2                1      0   Ok     18      6.2K
3.7K

One hit to script that generates the 500 (500 returned to browser):
   [1]http://127.0.0.1:8001 1                1      0   Err    21      7.3K
3.7K
   [2]http://127.0.0.1:8002 2                1      0   Ok     18      6.2K
3.7K

Several hits to valid script before 60 second retry time:
   [1]http://127.0.0.1:8001 1                1      0   Ok     34      12K 
3.9K
   [2]http://127.0.0.1:8002 2                1      0   Err    20      6.9K
4.8K

2 hits after retry time expired:
   [1]http://127.0.0.1:8001 1                1      0   Ok     35      12K 
3.9K
   [2]http://127.0.0.1:8002 2                1      0   Ok     21      7.3K
4.8K


At the same time, I ran a test case with several hits to the buggy CGI script -
as expected the force_recovery function forced the traffic through.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to