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

ProxyErrorOverride=On causes workers in error state after 500 errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • httpd 2.4.23 DR1
    • httpd 2.4.6 DR1
    • httpd
    • None
    • Release Notes
    • Hide
      When using ProxyErrorOverride to host custom error pages on Apache Httpd the worker will be marked as down if the backend replies with a 50x error code.

      This issue is resolved in JBoss Core Services 2.4.23.
      Show
      When using ProxyErrorOverride to host custom error pages on Apache Httpd the worker will be marked as down if the backend replies with a 50x error code. This issue is resolved in JBoss Core Services 2.4.23.
    • Workaround Exists
    • Hide

      Disable ProxyErrorOverride

      Show
      Disable ProxyErrorOverride
    • Hide

      -Configure httpd/mod_cluster with:
      ProxyErrorOverride On
      ErrorDocument 500 /500.html

      -Access a JBoss app that generates a 500.
      -Note worker error state on subsequent requests until next STATUS MCMP

      Show
      -Configure httpd/mod_cluster with: ProxyErrorOverride On ErrorDocument 500 /500.html -Access a JBoss app that generates a 500. -Note worker error state on subsequent requests until next STATUS MCMP

      When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example.

              rhn-engineering-jclere Jean-Frederic Clere
              rhn-support-aogburn Aaron Ogburn
              Karm Karm Karm Karm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: