[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-72) Management operation to disable then stop node or webapp

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/MODCLUSTER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464258#action_12464258 ] 

Brian Stansberry commented on MODCLUSTER-72:
--------------------------------------------

The back end server can track this itself as well. It can also track how many sessions are still alive.

> Management operation to disable then stop node or webapp
> --------------------------------------------------------
>
>                 Key: MODCLUSTER-72
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-72
>             Project: mod_cluster
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>
> A common use case is to try to drain sessions from a server before taking it offline. With mod_cluster you can partially do that by invoking the JMX operation to disable a node, but then you need to manually monitor the # of active sessions so you can know when to stop the node. We should simplify this by adding an operation that tells the node to do the full disable-monitor session count-stop operation itself.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira