Newly Added Cache Criteria Parameter Not Picked Up By Some Nodes In Cluster
(Doc ID 2854611.1)
Last updated on JUNE 20, 2023
Applies to:
Oracle WebCenter Sites - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Updated Cache Criteria Not Picked Up on All Nodes in Cluster
After adding a new parameter to cache criteria for a SiteEntry, the cache criteria is only taking affect in 1 node of the cluster.
e.g.
SiteEntry:
- pagename: TestPage
- Cache criteria: c,cid,ft_ss, param1
After update:
- Cache criteria: c,cid,ft_ss, param1, param2
However, on other cluster members, when requesting the page, with the new parameter, it does not create a new cache key, and returns cache for keys that do not have the new parameter:
e.g.
/sites/Satellite?pagename=TestPage&c=Page&cid=12345¶m1=test1
output: test1 generated Jan-1-2022
/sites/Satellite?pagename=TestPage&c=Page&cid=12345¶m1=test1
output: test1 generated Jan-1-2022
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |