Tomcat session changes after stopping module on cluster node

• Type: Bug
• Status: Verified
• Resolution: Unresolved
• Affects Version/s: 7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: None
• Component/s: Fault Tolerance > Clustering Framework
• Labels: None
• Fix Priority: 3
• QA Test Name:
  • LocalFile.ClusteringCache#CanModuleBeShutdownDuringReplicateSession
• QA Test Score: 4

Steps to Reproduce:

1. Follow setup and steps in LPS-73732 - "stopping osgi module (easy way)"
   • Master compatible test portlet test.session.replication.jar
2. After Step 16 ("Open created page "session replication test" in a new browser using URL of second node"), assert that the session Data string is the same as before disabling the module.

Expected Result:
Data string on second node does not change when the module is disabled on the first (master) node. Liferay Home matches first node.

Actual Result:
Data string is new on the second node faster master node module is stopped. Liferay Home matches second node.

Discovered when executing test 10b from Cluster Test Plan

Reproduced on:
Master: 27800770b780195b90da7e420bd1ee6e67e3f095