[MODCLUSTER-188] mod_cluster failover does not work for a /webappcontext when the / root context exists Created: 13/Oct/10  Updated: 08/Aug/14  Resolved: 15/Feb/11

Status: Closed
Project: mod_cluster
Component/s: None
Affects Version/s: 1.0.4.GA, 1.1.0.Beta1
Fix Version/s: 1.0.8, 1.1.2.Final

Type: Bug Priority: Major
Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
relates to JBPAPP-5237 MODCLUSTER-188 - mod_cluster failover... Closed
Superset
Workaround:
Workaround Exists
Workaround Description:

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



 Comments   
Comment by Igor Gilany [ 10/Dec/10 ]

Verified in 1.0.5.GA

Comment by Jean-Frederic Clere [ 15/Feb/11 ]

the fix has side effects

Comment by Jean-Frederic Clere [ 15/Feb/11 ]

Fixed r505 & r514 (1.0.x)

Comment by Michal Karm Babacek [ 08/Aug/14 ]

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
Generated at Mon Oct 15 10:06:12 EDT 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.