mod_cluster issues an ENABLE-APP too early in the webapp lifecycle
------------------------------------------------------------------
Key: MODCLUSTER-190
URL: https://jira.jboss.org/browse/MODCLUSTER-190
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Fix For: 1.0.5
mod_cluster uses START_EVENT instead of a AFTER_START_EVENT so it might ENABLE the application too early.
--
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
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.1.0.Final, 1.0.4.GA
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.
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