Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9493

mod_cluster returns "Bad Gateway" HTTP ErrorCode 502 with https

    Details

    • Type: Support Patch
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: EAP_EWP 5.1.1
    • Fix Version/s: One Off Releases
    • Component/s: mod_cluster
    • Labels:
      None
    • Environment:
      • Apache Webserver 2.2.15 from RHEL 6.2 with mod_cluster Native-Libs
      • patch mod_cluster-native-1.0.10-5.1.1.GA_CP02_patch02.ep5.el6.x86_64.rpm
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      This release of JBoss Enterprise Application Platform 5 resolves an issue that caused mod_cluster to return an HTTP error 502 (Bad Gateway) after a period of inactivity. Regular STATUS messages sent by cluster nodes prompted <literal>httpd</literal> to create a connection to the node and attempt a ping. These connections are reused in <literal>httpd</literal>. The bug was triggered by the use of these connections by subsequent browser requests, as they did not use SSL. This caused the node to reject the request with an SSL error and <literal>httpd</literal> to return the 502 error. The fix implemented ensures that connections are initialized correctly and avoids the error.
      Show
      This release of JBoss Enterprise Application Platform 5 resolves an issue that caused mod_cluster to return an HTTP error 502 (Bad Gateway) after a period of inactivity. Regular STATUS messages sent by cluster nodes prompted <literal>httpd</literal> to create a connection to the node and attempt a ping. These connections are reused in <literal>httpd</literal>. The bug was triggered by the use of these connections by subsequent browser requests, as they did not use SSL. This caused the node to reject the request with an SSL error and <literal>httpd</literal> to return the 502 error. The fix implemented ensures that connections are initialized correctly and avoids the error.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      After a longer pause with no requests (e.g. in the morning) I get back an HTTP Error Code 502 (Bad Gateway)
      The community thread https://community.jboss.org/thread/177386?start=0&tstart=0 describes the issue.
      Attached you will find a snippet where the "Bad Request" was sent to the Apache Webserver (http-Log-file)

      After multiple requests, the error is gone and everything works fine. Just after a longer pause the error comes back.

      it seems that the "Bad Gateway" message and the SSL-Error is gone if we set the following Attribute in the mod-cluster-jboss-beans.xml
      <property name="stickySessionRemove">true</property> - default Value is "false"

      Why does stickySessionRemove work ? It's odd, as there doesn't seem to be a clear link.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  lakagwu Lami Akagwu
                  Reporter:
                  lakagwu Lami Akagwu
                  Writer:
                  Scott Thomas
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: