Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-380

failonstatus parameter ignored


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • httpd 2.4.23 GA, httpd 2.4.23 SP1 GA
    • mod_cluster
    • None

      Setting failonstatus to a specific code should result in the error state of the worker that returned the code.

      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 response code: was 200, expected [200, 201, 202, 203]

      Let's send special request that returns 201(failonstatus code)

      Checking for response code: was 201, expected 201

      This should result in worker in error state

      <h1> Node tomcat-7-1 (ajp:// </h1>
      ...Status: NOTOK,Elected: 13,Read: 245,Transferred: 0,Connected: 0,Load: 100...
      ><h1> Node tomcat-7-2 (ajp:// </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] balancer://balancerxxx: Forcing worker (ajp:// into error state due to status code 201 matching 'failonstatus' balancer parameter

      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.

            mbabacek1@redhat.com Michal Karm
            bsikora Bogdan Sikora (Inactive)
            Jan Kašík Jan Kašík
            0 Vote for this issue
            5 Start watching this issue