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 OCTOBER 02, 2024

Applies to:

Oracle Coherence - Version 3.7.1.19 and later
Oracle Access Manager - Version 11.1.2.2.0 and later
Information in this document applies to any platform.

Goal

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?

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How to ensure the OAM session Coherence cache data timeout is same OAM console session timeout, 1800 seconds? (Doc ID 2705539.1)

Applies to:

Goal

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!