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

mod_proxy_hcheck should be aware of BalancerMember's connectiontimeout parameter and should timeout based on it.

    Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: httpd 2.4.23 GA
    • Fix Version/s: httpd 2.4.37 ER1
    • Component/s: httpd, jbcs-httpd24-httpd
    • Labels:
      None
    • Environment:

      Software platform: This issue was found on RHEL 7 x86_64 but it is independent of software platform.

      Description

      When connectiontimeout parameter is given to BalancerMember directive like the following, mod_proxy_hcheck is not aware of the connectiontimeout parameter. Therefore, in case that the network is unreachable, the worker for health-check does not timeout in connectiontimeout seconds even though the worker for real HTTP request to the same backend timeouts in connectiontimeout seconds. mod_proxy_hcheck should be aware of BalancerMember's connectiontimeout parameter and should timeout based on it.

      <VirtualHost *:80>
        ...(snip)...
        ProxyPass /A balancer://webapps/A
      </VirtualHost>
      
      <Proxy balancer://webapps>
        BalancerMember http://<host1_ipaddress>:<host1_port> route=jvm1 loadfactor=10 connectiontimeout=15 hcmethod=TCP hcinterval=5 hcpasses=2 hcfails=3
        BalancerMember http://<host2_ipaddress>:<host2_port> route=jvm2 loadfactor=10 connectiontimeout=15 hcmethod=TCP hcinterval=5 hcpasses=2 hcfails=3
        ProxySet stickysession=JSESSIONID|jsessionid
      </Proxy>
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                gzaronikas George Zaronikas
                Reporter:
                myoshida Masato Yoshida
                Tester:
                Paul Lodge
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: