[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies

[Paul Ferraro (JIRA)]

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

Paul Ferraro commented on MODCLUSTER-125:
-----------------------------------------

I imagined the default value actually being something like: ${jboss.mod_cluster.auto-enable-contexts:true}
So, true by default, but able to be overridden via a system property.
Rather than updating the config file while the server is running, you would simply restart the node with:
-Djboss.mod_cluster.auto-enable-contexts=false
Then, once the server is validated, manually call the enable() mbean method.

> Permanently remove a JBoss node from configured http proxies
> ------------------------------------------------------------
>
>                 Key: MODCLUSTER-125
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-125
>             Project: mod_cluster
>          Issue Type: Feature Request
>    Affects Versions: 1.0.3.GA, 1.1.0.Beta1, 1.1.0.CR1
>            Reporter: Ben Schofield
>            Assignee: Paul Ferraro
>             Fix For: 1.1.0.CR1
>
>
> When a JBoss node is restarted it advertises the web apps deployed to it as being available for the http proxy to route traffic to them.  This is undesirable when a JBoss administrator needs to keep a JBoss node out of service for validation and/or troubleshooting steps.  Mod_cluster needs to offer some mechanism to permanently remove a JBoss node from any configured http proxy until a JBoss administrator manually adds it back.

-- 
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