]
Radoslav Husar updated WFLY-5764:
---------------------------------
Workaround Description: Workaround for excluding no contexts is to set
"excluded-contexts" to non-sense random value that will not match any real
context.
Workaround: Workaround Exists
Remove mod_cluster excluded-context's default value with outdated
contexts
--------------------------------------------------------------------------
Key: WFLY-5764
URL:
https://issues.jboss.org/browse/WFLY-5764
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR4
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 10.0.0.CR5
The list of current values is useless in the defualt configuration.
{code}"excluded-contexts" =>
"ROOT,invoker,jbossws,juddi,console"{code}
I am actually marking this as bug, because if you just want to use the root context, if
you undefine the value, the default will be used which exludes root context.
Trying a "" value, results in a failure.
{code}[standalone@localhost:9990 /]
/subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value=""
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0113: '' is an invalid
value for parameter excluded-contexts. Values must have a minimum length of 1
characters",
"rolled-back" => true,
"response-headers" => {"process-state" =>
"reload-required"}
}{code}
This all comes from legacy stuff.