[ https://jira.jboss.org/browse/MODCLUSTER-189?page=com.atlassian.jira.plug... ] Henrik Aronsen updated MODCLUSTER-189: -------------------------------------- Summary: Enable/Disable does not work in mod_cluster_manager (was: Enable/disable does not work in mod_cluster_manager) Description: 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. was: When I disable a context in mod_cluster_manager nothing happens: the context is still available. 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

[ https://jira.jboss.org/browse/MODCLUSTER-189?page=com.atlassian.jira.plug... ] Jean-Frederic Clere resolved MODCLUSTER-189. -------------------------------------------- Resolution: Rejected DISABLE: Apache httpd should not create new session for this webapp, but still continue serving existing session on this node. -- 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