Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-675

Failover scenario is not performed with httpd balancer - balancer fails to respond

XMLWordPrintable

    • Hide
      1. Prepare configuration with one balancer (Apache 2.4.29) and workers (Wildfly/EAP)
      2. Send request to balancer and obtain JSESSIONID (e.g. 54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3)
      3. Kill worker which handled the request
      4. Make another request with same JSESSIONID
      Show
      Prepare configuration with one balancer (Apache 2.4.29) and workers (Wildfly/EAP) Send request to balancer and obtain JSESSIONID (e.g. 54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3 ) Kill worker which handled the request Make another request with same JSESSIONID

      When second request in failover scenario is made to check whether the failover was done, server fails to respond. With Undertow as a balancer, this behavior cannot be reproduced. When I replace the jvmroute part by worker which is still alive, I got expected response.

      # curl -v --cookie "JSESSIONID=54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3" http://172.17.0.2:2080/clusterbench/jvmroute
      * About to connect() to 172.17.0.2 port 2080 (#0)
      *   Trying 172.17.0.2...
      * Connected to 172.17.0.2 (172.17.0.2) port 2080 (#0)
      > GET /clusterbench/jvmroute HTTP/1.1
      > User-Agent: curl/7.29.0
      > Host: 172.17.0.2:2080
      > Accept: */*
      > Cookie: JSESSIONID=54yxdncGr5im0fBLqIIUMon0klbS66X16aYC_cVW.jboss-eap-7.2-3
      >
      * Empty reply from server
      * Connection #0 to host 172.17.0.2 left intact
      curl: (52) Empty reply from server
      

        1. error_log
          26 kB
        2. wildfly-16.0.0.Beta1-SNAPSHOT.zip
          120 kB
        3. httpd.zip
          36 kB

            rhn-engineering-jclere Jean-Frederic Clere
            jkasik@redhat.com Jan Kašík
            Jan Kašík Jan Kašík
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: