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

Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy

    XMLWordPrintable

Details

    • Hide
      1. Start Wildfly with standalone-ha.xml profile
      2. [standalone@localhost:9990 /] /subsystem=modcluster/:disable
{
    "outcome" => "failed",
    "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.",
    "rolled-back" => true
}
      Show
      Start Wildfly with standalone-ha.xml profile [standalone@localhost:9990 /] /subsystem=modcluster/:disable { "outcome" => "failed" , "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address." , "rolled-back" => true }
    • User Experience
    • Workaround Exists
    • Hide 
      [standalone@localhost:9990 /] /subsystem=modcluster/proxy=default:disable
{
    "outcome" => "success",
    "result" => false
}
      Show
      [standalone@localhost:9990 /] /subsystem=modcluster/proxy= default :disable { "outcome" => "success" , "result" => false }

    Description

      Running legacy operation ends up with an error:

      [standalone@localhost:9990 /] /subsystem=modcluster/:disable
{
    "outcome" => "failed",
    "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.",
    "rolled-back" => true
}

      mod_cluster configuration:

      [standalone@localhost:9990 /] /subsystem=modcluster/:read-resource
{
    "outcome" => "success",
    "result" => {
        "mod-cluster-config" => {"configuration" => undefined},
        "proxy" => {"default" => undefined}
    }
}

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15629 Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11135 Object, instead of a simple boolean should be returned by stop operation on mod_cluster

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              jkasik@redhat.com Jan Kašík
              Jan Kašík Jan Kašík
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: