Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-188

mod_cluster failover does not work for a /webappcontext when the / root context exists

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.0.4.GA, 1.1.0.Beta1
    • Fix Version/s: 1.0.8, 1.1.2.Final
    • Component/s: None
    • Labels:
      None
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Either
      A) don't deploy a / or smaller path
      B) Use ProxyPass/ProxyPassReverse in Apache to map / to a difference context in JBoss/mod_cluster but don't actually use / in JBoss.

      Show
      Either A) don't deploy a / or smaller path B) Use ProxyPass/ProxyPassReverse in Apache to map / to a difference context in JBoss/mod_cluster but don't actually use / in JBoss.

      Description

      Let's say for example that /webapp and / is mapped in mod_cluster and there are two JBoss instances. If in one JBoss instance you undeploy the /webapp, you would expect mod_cluster to failover to the other JBoss instance.

      However, this is not the case, mod_cluster will instead select the lesser context, the root context / and service the request from /webapp on the / context.

      The logic only tests for ENABLE and DISABLE the STOP is not tested.

      The failover of a context will only work currently if / or any smaller path is not deployed

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jfclere Jean-Frederic Clere
                  Reporter:
                  sjmenden Samuel Mendenhall
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: