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

[Michal Babacek (JIRA)]

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

Michal Babacek closed MODCLUSTER-188.
-------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> 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
>      Security Level: Public(Everyone can see) 
>    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 was sent by Atlassian JIRA
(v6.2.6#6264)