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

Update out-of-date and fix CLI script examples in mod_cluster section

XMLWordPrintable

      fmarchio@redhat.com found an out of date example:

      /subsystem=modcluster/proxy=default:read-resource(name=mod-cluster-config)
      {
      "outcome" => "success",
      "result" => {"simple-load-provider" => {"factor" => "1"}}
      }
      On a fresh WF 27 HA I see:
      "load-provider" =>

      {"dynamic" => undefined}

      And mod-cluster-config parameter is no longer available.

      Also, I have noticed some other broken CLI scripts

      [standalone@localhost:9990 /] /subsystem=undertow/server=other-server/host=other-host:write-attribute(name=alias, value=[localhost]))
      ')' is not a valid node type name.

      or

      [standalone@localhost:9990 /] /subsystem=modcluster/proxy=other:add(advertise-socket=modcluster-other, balancer=other-balancer, connector=ajp-other)
      'connector' is not found among the supported properties: [advertise, advertise-security-key, advertise-socket, auto-enable-contexts, balancer, excluded-contexts, flush-packets, flush-wait, listener, load-balancing-group, max-attempts, node-timeout, ping, proxies, proxy-url, session-draining-strategy, smax, socket-timeout, ssl-context, status-interva
      l, sticky-session, sticky-session-remove, sticky-session-force, stop-context-timeout, ttl, worker-timeout]

      or

      [standalone@localhost:9990 /] /subsystem=modcluster/proxy=default:remove-metric(type=cpu)
      Failed to get the list of the operation properties: "WFLYCTL0162: There is no operation remove-metric registered at address [
      ("subsystem" => "modcluster"),
      ("proxy" => "default")
      ]"

      and many more.

      Also, remove domain examples and use standalone instead.

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

                Created:
                Updated:
                Resolved: