[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-220) Extra ENABLE-APP/REMOVE-APP event after failover
Michal Babacek (JIRA)
jira-events at lists.jboss.org
Fri Jun 10 09:04:59 EDT 2011
[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607830#comment-12607830 ]
Michal Babacek commented on MODCLUSTER-220:
-------------------------------------------
It's easy to reproduce with [jboss-ews-1.0.2_CR4-RHEL5-x86_64.zip|http://download.devel.redhat.com/devel/candidates/JBEWS/JBEWS-1.0.2-CR4/jboss-ews-1.0.2_CR4-RHEL5-x86_64.zip].
*Steps*
# Start httpd
# Start Tomcat6 _(perf03)_
# Start Tomcat6 _(perf04)_
# Wait ~3min
# kill -9 <Tomcat6 _(perf03)_' PID>
# Wait ~2min
# Start Tomcat6 _(perf03)_
Note: There were no requests issued to any of the aforementioned nodes, nor to the Mod_Cluster manager web page.
{code:title=access_log|borderStyle=solid}
...
10.16.88.182 - - [10/Jun/2011:08:35:19 -0400] "STATUS / HTTP/1.0" 200 56 "-" "ClusterListener/1.0"
10.16.88.181 - - [10/Jun/2011:08:35:28 -0400] "INFO / HTTP/1.0" 200 1143 "-" "ClusterListener/1.0"
10.16.88.181 - - [10/Jun/2011:08:35:28 -0400] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
10.16.88.181 - - [10/Jun/2011:08:35:28 -0400] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
10.16.88.181 - - [10/Jun/2011:08:35:28 -0400] "REMOVE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
10.16.88.181 - - [10/Jun/2011:08:35:28 -0400] "STATUS / HTTP/1.0" 200 56 "-" "ClusterListener/1.0"
...
{code}
{code:title=error_log (debug)|borderStyle=solid}
[Fri Jun 10 08:35:19 2011] [debug] mod_manager.c(1988): manager_handler STATUS OK
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1432): manager_trans INFO (/)
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1947): manager_handler INFO (/) processing: ""
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1988): manager_handler INFO OK
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1432): manager_trans CONFIG (/)
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1947): manager_handler CONFIG (/) processing: "JVMRoute=perf03&Port=8009&Host=10.16.88.181&Type=ajp&StickySessionForce=No&StickySessionRemove=Yes"
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1988): manager_handler CONFIG OK
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1432): manager_trans ENABLE-APP (/)
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1947): manager_handler ENABLE-APP (/) processing: "JVMRoute=perf03&Alias=localhost&Context=%2f"
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1988): manager_handler ENABLE-APP OK
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1432): manager_trans REMOVE-APP (/)
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1947): manager_handler REMOVE-APP (/) processing: "JVMRoute=perf03&Alias=localhost&Context=%2f"
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1988): manager_handler REMOVE-APP OK
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1432): manager_trans STATUS (/)
[Fri Jun 10 08:35:28 2011] [debug] mod_manager.c(1947): manager_handler STATUS (/) processing: "JVMRoute=perf03&Load=99"
[Fri Jun 10 08:35:28 2011] [debug] proxy_util.c(2011): proxy: ajp: has acquired connection for (10.16.88.181)
{code}
All log and configuration files from both Tomcat and Httpd nodes are available for [download|http://scratch.englab.brq.redhat.com/mbabacek/MODCLUSTER-220/].
> 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
More information about the mod_cluster-issues
mailing list