[jboss-jira] [JBoss JIRA] (WFLY-5018) Undertow mod_cluster CLI: Control Node: Enable Contexts, Disable Contexts, Stop Contexts

[Stuart Douglas (JIRA)]

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

Stuart Douglas moved UNDERTOW-496 to WFLY-5018:
-----------------------------------------------

              Project: WildFly  (was: Undertow)
                  Key: WFLY-5018  (was: UNDERTOW-496)
           Issue Type: Feature Request  (was: Bug)
    Affects Version/s:     (was: 1.3.0.Beta3)
          Component/s: Web (Undertow)
                           (was: Proxy)


> Undertow mod_cluster CLI: Control Node: Enable Contexts, Disable Contexts, Stop Contexts
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-5018
>                 URL: https://issues.jboss.org/browse/WFLY-5018
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web (Undertow)
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>            Priority: Critical
>              Labels: mod_cluster
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Control Nodes
> For any  Undertow mod_cluster proxy environment, it is essential to be able to Enable Contexts, Disable Contexts and Stop Contexts on a selected worker Node.
> It is an equivalent of sending this MCMP message attributes ({{worker-2}} is an arbitrary worker node's JVMRoute): 
> * Enable Contexts {{Cmd=ENABLE-APP&Range=NODE&JVMRoute=worker-2}}
> * Disable Contexts {{Cmd=DISABLE-APP&Range=NODE&JVMRoute=worker-2}}
> * Stop Contexts {{Cmd=STOP-APP&Range=NODE&JVMRoute=worker-2}}
> h3. Call to action
> Enable user to carry out these actions via WildFly CLI.



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