Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-362

ProxyErrorOverride=On causes workers in error state after 500 errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • JWS 3.0.2 GA
    • httpd
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Documented as Known Issue
    • 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:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: