Bug 1377246

Summary: session.invalidate does not work on cluster enabled webapps
Product: Red Hat Enterprise Linux 7 Reporter: Dasharath Masirkar <dmasirka>
Component: tomcatAssignee: Coty Sutherland <csutherl>
Status: CLOSED CURRENTRELEASE QA Contact: Michal Karm Babacek <mbabacek>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 7.2CC: dpuglielli, joni.lapilainen, mbabacek, pbajenez, rbost, rhatlapa
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-21 16:37:46 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:
Attachments:
Description Flags
Simple web app to reproduce the issue none

Description Dasharath Masirkar 2016-09-19 09:49:14 UTC 
Created attachment 1202414 [details]
Simple web app to reproduce the issue

Description of problem:
session.invalidate does not work on cluster enabled webapps (the application web.xml with <distributable/> element) when Tomcat is clustered. In standalone instance it works fine.

Version-Release number of selected component (if applicable):
tomcat-7.0.54-2.el7_1

How reproducible:
Always

Steps to Reproduce:
1.Use Clustered Tomcat, with the following added to the <Host/> in server.xml:
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>

2.Deploy attached TestApp.war to the tomcat webapps
3.Open session.jsp in a web browser (http://127.0.0.1:8080/TestApp/session.jsp). Note creation time.
4.Refresh page and note creation time stays the same.
5.Click on Invalidate and note that creation time is not updated.

Actual results:
When click on Invalidate, the creation time is not updated.

Expected results:
When click on Invalidate, the creation time must be updated.

Additional info:
This is captured as upstream bug https://bz.apache.org/bugzilla/show_bug.cgi?id=56578 and has been fixed in 7.0.55 onwards.
Comment 10 Coty Sutherland 2016-11-21 16:37:46 UTC 
This issue has been fixed and the case associated with the zstream request is now closed. I'm closing this as rhel-7.3.0 has been released with the fix. If there is need for a zstream fix, we can revisit this.