Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
1.3.5.Final
-
None
Description
Setting failonstatus to a specific code should result in the error state of the worker that returned the code.
Example:
Httpd mod_cluster balancer with 2 tomcat workers that have deployed clusterbench app
ProxyPass / balancer://balancerxxx stickysession=JSESSIONID|jsessionid nofailover=on failonstatus=201 ProxyPassReverse / balancer://balancerxxx ProxyPreserveHost on
Checking for http://192.168.122.206:2080/clusterbench/jvmroute response code: was 200, expected [200, 201, 202, 203]
Let's send special request that returns 201(failonstatus code)
Checking for http://192.168.122.206:2080/clusterbench/httpcode/?http_code=201 response code: was 201, expected 201
This should result in worker in error state
<h1> Node tomcat-7-1 (ajp://192.168.122.206:8009): </h1> ...Status: NOTOK,Elected: 13,Read: 245,Transferred: 0,Connected: 0,Load: 100... ><h1> Node tomcat-7-2 (ajp://192.168.122.206:8110): </h1> ...Status: OK,Elected: 1,Read: 10,Transferred: 0,Connected: 0,Load: 100...
as in example. This example is made with 2.4.6 httpd.
Debug log
[Wed Jul 26 09:13:12.646541 2017] [:error] [pid 22223] [client 192.168.122.206:41482] balancer://balancerxxx: Forcing worker (ajp://192.168.122.206:8009) into error state due to status code 201 matching 'failonstatus' balancer parameter
Issue:
2.4.23+ Httpd ignores failonstatus parameter.
Return of 201 as in example trigger no error state.
There is no mention in the log and workers on the console are in OK state.
Attachments
Issue Links
- clones
-
-
- Closed
-
