[mod_cluster-issues] [JBoss JIRA] Resolved: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Wed Mar 3 14:17:10 EST 2010
[ https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro resolved MODCLUSTER-125.
-------------------------------------
Resolution: Done
Added autoEnableContexts property that defaults to true.
If false, contexts are registered with mod_cluster as disabled.
This value can be toggled during AS startup via the -Djboss.mod_cluster.autoEnableContexts system property.
> 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
More information about the mod_cluster-issues
mailing list