[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-220: -------------------------------------- Summary: Extra ENABLE-APP/REMOVE-APP event after failover (was: Extra REMOVE-APP event after failover) Affects Version/s: 1.0.8 Environment: Deployment on Tomcat6 Priority: Major (was: Trivial) This is a Tomcat deplyment, so its non-HA (which is not supported on Tomcat). I updated the Jira accordingly. I cant judge the severity of the issue but a race condition might trigger 404. Do the apps have also a state which is propagated in ENABLE-APP event? I don't think that's the case meaning its useless to remove and add back from the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-220: ------------------------------------------- It was -9, ok I will try again later and post more info. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-220: ------------------------------------------- Fix Version/s: 1.0.10 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-220: ------------------------------------------- Fix Version/s: MOD_CLUSTER_1_0_10_GA_CP (was: 1.0.11) Affects Version/s: 1.0.10 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-220: ----------------------------------------- Assignee: Michal Babacek (was: Radoslav Husar) Michal can you have a look and if you cant reproduce then just close it? Note this was tried on Tomcat. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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]... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-220: ------------------------------------------------ "It's easy to reproduce with jboss-ews-1.0.2_CR4-RHEL5-x86_64.zip." That seems to be the only Tomcat that shows the problem :-( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-220. -------------------------------------------- Resolution: Done Fixed by r599/r601 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Michal Babacek commented on MODCLUSTER-220: ------------------------------------------- To be verified... ;-) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/MODCLUSTER-220?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-220: -------------------------------------- Issue Type: Bug (was: Enhancement) Description: 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} was: 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} Updating Issue Type to Bug as per comments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira