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

Failover triggers 500 Internal Server Error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • EAP 5.0.0 mod_cluster
    • EAP 5.0.0
    • mod_cluster
    • None

    • perf lab

    • Documentation (Ref Guide, User Guide, etc.), Release Notes

      Related to JBPAPP-3614 but more severe.

      Simple scenario: mod_cluster and 4 JBoss nodes are deployed. When a JBoss server fails (JVM is forcibly killed), several sessions result in error 500 - Internal Server Error. It happens exactly at the time of killing one node.

      <html><head>
      <title>500 Internal Server Error</title>
      </head><body>
      <h1>Internal Server Error</h1>
      <p>The server encountered an internal error or
      misconfiguration and was unable to complete
      your request.</p>
      ....
      <address>Apache/2.2.10 (Red Hat) Server at hudson1 Port 8888</address>
      </body></html>

      Hudson job:
      http://hudson.qa.jboss.com/hudson/view/mod_cluster-QE/job/eap-50-mod_cluster-failover-rhel5-x86_64/38/

              rhn-engineering-jclere Jean-Frederic Clere
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: