[jboss-jira] [JBoss JIRA] (WFLY-4984) Undertow mod_cluster CLI: Display balancer's stickySession, stickySessionRemove, stickySessionForce, waitWorker and maxattempts properties

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas moved UNDERTOW-492 to WFLY-4984:
-----------------------------------------------

              Project: WildFly  (was: Undertow)
                  Key: WFLY-4984  (was: UNDERTOW-492)
    Affects Version/s:     (was: 1.3.0.Beta3)
          Component/s: Web (Undertow)
                           (was: Proxy)


> Undertow mod_cluster CLI: Display balancer's stickySession, stickySessionRemove, stickySessionForce, waitWorker and maxattempts properties
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4984
>                 URL: https://issues.jboss.org/browse/WFLY-4984
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>            Priority: Minor
>              Labels: mod_cluster
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing CLI management capabilities. It is of {color:green}Minor{color} priority though.
> h3. Display balancer's stickySession, stickySessionRemove, stickySessionForce, waitWorker and maxattempts properties
> At the moment, this is all there is to see as far as *balancer* runtime configuration goes:
> {noformat}
> "balancer" => {
>     "qa_balancer" => {"node" => {"worker-2" => {
>         "load" => 89,
>         "status" => "NODE_UP",
>         "context" => {"/clusterbench" => {
>             "requests" => 0,
>             "status" => "enabled"
>         }}
>     }}},
> ...
> {noformat}
> h3. Call to action
> Display runtime configuration properties for each balancer; especially these concerning session stickiness. It would help users debug their complex highly available environments without having to dauntingly parse DEBUG logs.   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)