How to ensure the OAM session Coherence cache data timeout is same OAM console session timeout, 1800 seconds?
(Doc ID 2705539.1)
Last updated on SEPTEMBER 02, 2020
Applies to:Oracle Coherence - Version 188.8.131.52 and later
Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In a JDE integrated OAM domain, session expiration is happening prematurely. The intended time is 1800 seconds, but the there is a doubt that OAM cache entries are missing before that time intermittently. What is that relevant cache data configuration that is different from OAM session timeout 1800 seconds?
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