[mod_cluster-issues] [JBoss JIRA] Updated: (MODCLUSTER-188) mod_cluster failover does not work for a /webappcontext when the / root context exists

[Jean-Frederic Clere (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Frederic Clere updated MODCLUSTER-188:
-------------------------------------------

    Fix Version/s: 1.0.8
                   1.1.2.Final 
                       (was: 1.0.5)
                       (was: 1.1.1.Final)


> mod_cluster failover does not work for a /webappcontext when the / root context exists
> --------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-188
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-188
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.0.4.GA, 1.1.0.Beta1
>            Reporter: Samuel Mendenhall
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.0.8, 1.1.2.Final 
>
>
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira