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

Details

    • 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

    Description

      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

      Attachments

        1. error_log
          26 kB
          Jan Kašík

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBCS-710 Failover scenario is not performed with httpd balancer - balancer fails to respond

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-697 Segfault when DeterministicFailover On

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBCS-798 Segfault when DeterministicFailover On

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              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

              Dates

                Created:
                Updated:
                Resolved: