7:32 a.m.
[
https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl...
]
Michal Babacek commented on MODCLUSTER-220:
-------------------------------------------
Well...does it look like:
{noformat}
mod_manager.c(1988): manager_handler STATUS OK
mod_manager.c(1432): manager_trans INFO (/)
mod_manager.c(1947): manager_handler INFO (/) processing: ""
mod_manager.c(1988): manager_handler INFO OK
mod_manager.c(1432): manager_trans CONFIG (/)
mod_manager.c(1947): manager_handler CONFIG (/) processing:
"JVMRoute=perf03&Port=8009&Host=10.16.88.181&Type=ajp&StickySessionForce=No&StickySessionRemove=Yes"
mod_manager.c(1988): manager_handler CONFIG OK
mod_manager.c(1432): manager_trans ENABLE-APP (/)
mod_manager.c(1947): manager_handler ENABLE-APP (/) processing:
"JVMRoute=perf03&Alias=localhost&Context=%2f"
mod_manager.c(1988): manager_handler ENABLE-APP OK
mod_manager.c(1432): manager_trans REMOVE-APP (/)
mod_manager.c(1947): manager_handler REMOVE-APP (/) processing:
"JVMRoute=perf03&Alias=localhost&Context=%2f"
mod_manager.c(1988): manager_handler REMOVE-APP OK
mod_manager.c(1432): manager_trans STATUS (/)
mod_manager.c(1947): manager_handler STATUS (/) processing:
"JVMRoute=perf03&Load=99"
{noformat}
*Reader's Digest:*
...
mod_manager.c(1947): manager_handler ENABLE-APP \(/) processing:
"JVMRoute=perf03&Alias=localhost&Context=%2f"
mod_manager.c(1947): manager_handler REMOVE-APP \(/) processing:
"JVMRoute=perf03&Alias=localhost&Context=%2f"
...
We are trying to narrow it down with [~jfclere]...
Extra ENABLE-APP/REMOVE-APP event after failover
------------------------------------------------
Key: MODCLUSTER-220
URL: https://issues.jboss.org/browse/MODCLUSTER-220
Project: mod_cluster
Issue Type: Enhancement
Affects Versions: 1.0.8, 1.0.10
Environment: Deployment on Tomcat6
Reporter: Radoslav Husar
Assignee: Michal Babacek
Fix For: MOD_CLUSTER_1_0_10_GA_CP02
Trivial thing: I think there is an extra REMOVE-APP event happening after fail-over. The
test scenario is simple - start a node with 6 context, kill the node and reconnect. The
apps are unchanged but 5 are remembered as were and one is removed and added back? Since
they happen at the same time it looks like it happens uselessly and can cause race
condition.
{code}
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "INFO / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "CONFIG / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "STATUS / HTTP/1.0" 200 58
"-" "ClusterListener/1.0"
...
127.0.0.1 - - [04/Apr/2011:19:19:03 +0200] "GET /SessionTest/SessionTestServlet?
HTTP/1.1" 200 1 "-" "Jakarta Commons-HttpClient/3.1"
...
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "INFO / HTTP/1.0" 200 575
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "CONFIG / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "REMOVE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "STATUS / HTTP/1.0" 200 58
"-" "ClusterListener/1.0"
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira