[
https://issues.jboss.org/browse/MODCLUSTER-125?page=com.atlassian.jira.pl...
]
Michal Babacek closed MODCLUSTER-125.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
Permanently remove a JBoss node from configured http proxies
------------------------------------------------------------
Key: MODCLUSTER-125
URL:
https://issues.jboss.org/browse/MODCLUSTER-125
Project: mod_cluster
Issue Type: Feature Request
Security Level: Public(Everyone can see)
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 was sent by Atlassian JIRA
(v6.2.6#6264)