Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5764

Remove mod_cluster excluded-context's default value with outdated contexts

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.CR5
    • 10.0.0.CR4
    • Clustering
    • None
    • Workaround Exists
    • Hide

      Workaround for excluding no contexts is to set "excluded-contexts" to non-sense random value that will not match any real context.

      Show
      Workaround for excluding no contexts is to set "excluded-contexts" to non-sense random value that will not match any real context.

    Description

      The list of current values is useless in the defualt configuration.

      "excluded-contexts" => "ROOT,invoker,jbossws,juddi,console"

      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.

      [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"}
      }

      This all comes from legacy stuff.

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: