How To Enable Sticky Session In OBDx or Eliminate Session Replication Error In Clustered Environment ?
(Doc ID 2636180.1)
Last updated on AUGUST 25, 2022
Applies to:
Oracle Banking Digital Experience - Version 18.1.0.0.0 to 18.1.0.0.0 [Release 18]Information in this document applies to any platform.
Goal
How to enable sticky session in OBDx or eliminate session replication error ?. This might be because of errors in OBDx logs as below
WatchData: MESSAGE = [ServletContext@139556629[app:obdx.app.rest.idm module:digx path:null spec-version:3.1]] Servlet failed with an Exception
java.lang.AssertionError: Lookup returned replicated session object with a different sessionid
at weblogic.servlet.internal.session.ReplicatedSessionContext.lookupSession(ReplicatedSessionContext.java:682)
at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:384)
at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:376)
Solution
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
| Goal |
| Solution |
| References |