[
https://issues.jboss.org/browse/MODCLUSTER-190?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-190:
------------------------------------------------
In fact in 1.1.x if a test application I have:
+++
[Wed Dec 15 15:27:10 2010] [debug] mod_manager.c(1610): manager_trans ENABLE-APP (/)
[Wed Dec 15 15:27:10 2010] [debug] mod_manager.c(2239): manager_handler ENABLE-APP (/)
processing:
"JVMRoute=4e6189af-0502-3305-8ff3-fad7fee8b516&Alias=localhost&Context=%2Fmyapp"
[Wed Dec 15 15:27:10 2010] [debug] mod_manager.c(2282): manager_handler ENABLE-APP OK
[Wed Dec 15 15:28:40 2010] [debug] mod_manager.c(1610): manager_trans ENABLE-APP (/)
[Wed Dec 15 15:28:40 2010] [debug] mod_manager.c(2239): manager_handler ENABLE-APP (/)
processing:
"JVMRoute=4e6189af-0502-3305-8ff3-fad7fee8b516&Alias=localhost&Context=%2Fmyapp"
[Wed Dec 15 15:28:40 2010] [debug] mod_manager.c(2282): manager_handler ENABLE-APP OK
+++
The first is wrong (it is just after the CONFIG so that application can't be started
at that time. The second one is ok and occurs at the right moment (that was what was fixed
in 1.0.5).
mod_cluster issues an ENABLE-APP too early in the webapp lifecycle
------------------------------------------------------------------
Key: MODCLUSTER-190
URL:
https://issues.jboss.org/browse/MODCLUSTER-190
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.4.GA, 1.1.0.Final
Reporter: Samuel Mendenhall
Assignee: Jean-Frederic Clere
Fix For: 1.0.5, 1.1.1.Final
Attachments: mod_cluster.patch
mod_cluster uses START_EVENT instead of AFTER_START_EVENT so it might ENABLE the
application too early.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira