Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899388 (JBEWS-297)

Summary: mod_cluster doesn't recognize when a webapp is started again after it had been stopped in Tomcat
Product: [JBoss] JBoss Enterprise Web Server 1 Reporter: Michal Karm Babacek <mbabacek>
Component: unspecifiedAssignee: Permaine Cheung <pcheung>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: EWS 1.0.2CC: jfclere, mbabacek, rhusar
Target Milestone: ---   
Target Release: EWS 1.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEWS-297
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Solaris 10, SPARC_64
Last Closed: 2011-06-17 20:36:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Mod_Cluster-httpdlog-Solaris10_SPARC_64.zip none

Description Michal Karm Babacek 2011-04-06 21:03:27 UTC 
project_key: JBEWS

The following behaviour was observed:

1) Httpd is aware of tomcat1 and tomcat2 nodes.
2) Requests to the load-demo webapp are being equally served both by tomcat1 and tomcat2.
3) Load-demo webapp is stopped with .../manager/html/stop?path=/load%2Ddemo... on tomcat2.
4) Only tomcat1 is serving requests now.
5) Load-demo webapp is started with .../manager/html/start?path=/load%2Ddemo... on tomcat2.
6) Only tomcat1 keeps serving requests, mod_cluster_manager shows load-demo webapp as STOPPED (however it is started at the moment)
7) If you disable & enable all contexts in the mod_cluster_manager, it "helps" the balancer to recognize that the webapp is started again and behaviour 2) takes place.
8) If you repeat step 3) again at this point, the balancer DOES NOT behave as described in 4), however you get HTTP 200 from tomcat1 and HTTP 404 from tomcat2 (balancer is switching between them)
Comment 1 Michal Karm Babacek 2011-04-06 21:09:31 UTC 
Log files describe the following scenario:

1) Requests are being issued to the balancer.

2) Webapp load-demo is stopped/started again on tomcat2 and tomcat1.

3) Tomcat1 (Tomcat2) is shut down and started again - gracefully.

4) Load-demo webapp is undeployed/deployed anain from/in Tomcat1 and Tomcat2.

5) Tomcat1 (Tomcat2) is killed by killing jvm's process.

All above but the stopping/starting the webapp on the Tomcat's manager page shown correct fail-over behaviour.

Note: STICKY SESSIONS: Switching them on/off in the Tomcat did not have any affect on the balancer's behaviour regarding the switching between tomcat1 and tomcat2; however I'm note sure whether it's a bug or a feature :-)
Comment 2 Michal Karm Babacek 2011-04-06 21:09:31 UTC 
Attachment: Added: Mod_Cluster-httpdlog-Solaris10_SPARC_64.zip
Comment 3 Jean-Frederic Clere 2011-04-07 08:41:14 UTC 
It seems the START for the /manager webapp doesn't send an ENABLE-APP...
Comment 4 Michal Karm Babacek 2011-04-07 17:31:55 UTC 
Gonna try if this proxy_ajp hint < https://issues.jboss.org/browse/JBPAPP-6257?focusedCommentId=12594319&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12594319 > can help it on Solaris...
Comment 5 Jean-Frederic Clere 2011-04-08 09:41:06 UTC 
Fix in mod_cluster 1.0.10 by r551
Comment 6 Jiri Skrabal 2012-11-13 16:27:17 UTC 
Docs QE Status: Removed: ASSIGNED