10:21 a.m.
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.1.0.Beta1, 1.0.3.GA, 1.1.0.CR1
Reporter: Ben Schofield
Assignee: Jean-Frederic Clere
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
12:06 p.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
Paul Ferraro updated MODCLUSTER-125:
------------------------------------
Fix Version/s: 1.1.0.CR1
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
12:06 p.m.
New subject: [JBoss JIRA] Assigned: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
Paul Ferraro reassigned MODCLUSTER-125:
---------------------------------------
Assignee: Paul Ferraro (was: Jean-Frederic Clere)
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
12:06 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
Paul Ferraro commented on MODCLUSTER-125:
-----------------------------------------
An auto-enable contexts flag, that defaults to true, should do the trick.
When this flag is disabled, we won't send any ENABLE-APP messages to the proxy.
Contexts will need to be manually enabled via the JMX interface.
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: Jean-Frederic Clere
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
2:02 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
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
4:02 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
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
6:30 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
Ben Schofield commented on MODCLUSTER-125:
------------------------------------------
Thanks Paul
Once something is implemented I will be available to test.
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
1:17 p.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-125) Permanently remove a JBoss node from configured http proxies
[
https://jira.jboss.org/jira/browse/MODCLUSTER-125?page=com.atlassian.jira...
]
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
5165
days inactive
5193
days old
mod_cluster-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Ben Schofield (JIRA) -
Paul Ferraro (JIRA)