Coherence*web Session Attribute lost intermittently in a Coherence*Web Cluster with the RequestDispatcher.forward calls in the WebApps
(Doc ID 2382002.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When attributes were added to an HTTP Session by means of Session Attribute add requests, it is observed that they are lost in subsequent requests. This happens only when there are both arms in the architecture (a primary and secondary are involved). However, when only one arm is in action (secondary switched off) the session attribute loss is not observed. User does not see this same behavior of losing session attributes at the time of single weblogic server is running in the coherence*web. The only difference found is how the primary JVM is defined within the session ID. In the case where we lose the attribute, we have the same primary JVM for almost every request leading up to where the xyz attribute is set. However, for the request that sets the xyz attribute the primary JVM ID is different. This is not so in the case when only the primary arm is involved. The same JVM ID is fully prevalent in this case.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document