Shared Application Module Cache Update Is Not Propagated In Cluster
(Doc ID 2496180.1)
Last updated on FEBRUARY 27, 2020
Applies to:Oracle JDeveloper - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
As part of an application, there are admin screens where users can add new values for the LOVs.
When Shared Application Module (Application Shared) is forced to refresh the cache, it works good on local instance. But in a cluster, it has been noticed that the cache is refreshed only on the managed server where the refresh was forced. The other managed server in the cluster does not get synced up.
1. The application is HA enabled.
2. The JSF Session scope is replicated across cluster seamlessly. If a new value is added into session on a page served by one of the managed servers, the session scope is synced across the JVMs in the cluster. A similar behavior is expected by the ADF Shared App Module.
Why is the Shared Application Module Cache update not propagated in Cluster ?
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