[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
Ben Schofield commented on MODCLUSTER-125:
------------------------------------------
So the process to permanently remove the node would be:
1) to set "auto-enable contexts" to false in mod-cluster-jboss-beans.xml
2) invoke the MBean to disable the node in the http proxy.
3) restart the node
do your validation
4) set "auto-enable contexts" to true in mod-cluster-jboss-beans.xml
5) invoke the mbean to enable the node in the http proxy.
Is that how you see things playing out? Any concern with triggering a deploy of
mod-cluster by modifying the config on the file system?
Of course "auto-enable contexts" could always be false if that is the desired
behavior. However this is only the desired behavior when something has gone wrong so I
wouldn't anticipate many folks setting "auto-enable contexts" to false as
the default.
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