Check the mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml
there should something like:
So it is -Djboss.modcluster.excludedContexts .... Note you try to use the default doing nothing should have work.
This line is unchanged by me and straight from the 1.1.3 tarball:
So, bot jboss.modcluster and jboss.mod_cluster should work, however I have also tried withhout the underscore with no luck.
However, my profile folder was a copy of the web profile, and I just tried renaming ROOT.war to jboss-ROOT.war, and excluded jboss-ROOT instead of just ROOT. Now it correctly excludes the context.
Is this a bug, or is it the correct behaviour? If it is correct behaviour, can I achieve the same without renaming ROOT.war, or is this rename required?
That looks like a bug :-(
Okay, then I'll file a bug report. We have a good workaround with the renaming of ROOT.war in the mean time.
I don't actually think this is a bug. Does your server.xml specify a specific host name, e.g. <Host name="myhost">?
The values contain in excludedContexts are expected to be host-delimited. If no host is specified, it is assumed to be "localhost".
To exclude the root context of a specific host, you would use something like this:
To elaborate, when parsing the excludedContexts, mod_cluster translates "ROOT" to the "" context, not "/". Jean-Frederic, is there a chance that the version of jbossweb in use here might be expecting "/" instead of ""?
We have in main/java/org/jboss/modcluster/mcmp/impl/ResetRequestSourceImpl.java:
path = "/";
I have localhost in my server.xml, and no aliases.
FYI, I tracked down the issue to a regression caused by MODCLUSTER-220. I've committed a fix, which will be included in 1.1.4.Final.