Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6005

[Proxy] No failover on empty response from node

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR8
    • 7.0.1.GA, 7.0.2.GA, 7.1.0.DR4
    • Undertow
    • None
    • It is now possible to configure max retries
    • Hide

      1. Start worker with servlet that has System.exit(1) call inside
      2. Start Eap as balancer
      3. Make request to servlet via balancer (curl BALANCER_ADDRESS:BALANCER_PORT/SERVLET)
      Expected :
      response with 50x response code
      Actual:
      No response, curl hang

      Show
      1. Start worker with servlet that has System.exit(1) call inside 2. Start Eap as balancer 3. Make request to servlet via balancer (curl BALANCER_ADDRESS:BALANCER_PORT/SERVLET) Expected : response with 50x response code Actual: No response, curl hang

      Undertow balancer do not recognizes empty response as an error.
      Can happen when JVM got killed when handling request (System.exit())

      @Override
        public void failed(final HttpServerExchange exchange) {
            final long time = System.currentTimeMillis();
            if (tries++ < maxRetryAttempts) { 
            ...

      Undertow make curl hang.
      Apache httpd correctly recognizes empty response as error and starts fail over method. If unsuccessful, 50x is returned in response.

            sdouglas1@redhat.com Stuart Douglas
            bsikora Bogdan Sikora (Inactive)
            Bogdan Sikora Bogdan Sikora (Inactive)
            Bogdan Sikora Bogdan Sikora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: