[
https://jira.jboss.org/browse/MODCLUSTER-189?page=com.atlassian.jira.plug...
]
Henrik Aronsen commented on MODCLUSTER-189:
-------------------------------------------
OK, I see that this only happens when I've established a session in the app/context.
Is there a way to disable the context and make clients with an active session fail over to
a different node? Or do I need to undeploy the app on the node in question to make that
work?
Enable/Disable does not work in mod_cluster_manager
---------------------------------------------------
Key: MODCLUSTER-189
URL:
https://jira.jboss.org/browse/MODCLUSTER-189
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Environment: Linux x86_64
Reporter: Henrik Aronsen
Assignee: Jean-Frederic Clere
When I disable a context in mod_cluster_manager nothing happens. The context is still
available even though it has Status: DISABLED.
I am using mod_cluster 1.1.0 with JBoss EAP 5.1. I've tried mod_cluster 1.0.4 and
JBoss EAP 5.0.0 as well. It's a pretty default setup, other than that I don't use
multicast: ServerAdvertise is Off and I've set the proxyList in
mod_cluster-jboss-beans.xml which points to my Apache frontend.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira