[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-608) failonstatus parameter ignored
Bogdan Sikora (JIRA)
issues at jboss.org
Fri Aug 4 04:12:00 EDT 2017
[ https://issues.jboss.org/browse/MODCLUSTER-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bogdan Sikora moved JBCS-381 to MODCLUSTER-608:
-----------------------------------------------
Project: mod_cluster (was: JBoss Core Services)
Key: MODCLUSTER-608 (was: JBCS-381)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Native (httpd modules)
(was: mod_cluster)
Affects Version/s: 1.3.5.Final
(was: httpd 2.4.23 GA)
(was: httpd 2.4.23 SP1 GA)
> failonstatus parameter ignored
> ------------------------------
>
> Key: MODCLUSTER-608
> URL: https://issues.jboss.org/browse/MODCLUSTER-608
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.3.5.Final
> Reporter: Bogdan Sikora
> Assignee: Michal Karm Babacek
>
> 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
> {noformat}
> ProxyPass / balancer://balancerxxx stickysession=JSESSIONID|jsessionid nofailover=on failonstatus=201
> ProxyPassReverse / balancer://balancerxxx
> ProxyPreserveHost on
> {noformat}
> {noformat}
> Checking for http://192.168.122.206:2080/clusterbench/jvmroute response code: was 200, expected [200, 201, 202, 203]
> {noformat}
> Let's send special request that returns 201(failonstatus code)
> {noformat}
> Checking for http://192.168.122.206:2080/clusterbench/httpcode/?http_code=201 response code: was 201, expected 201
> {noformat}
> This should result in worker in error state
> {noformat}
> <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...
> {noformat}
> as in example. This example is made with 2.4.6 httpd.
> Debug log
> {noformat}
> [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
> {noformat}
> *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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the mod_cluster-issues
mailing list