Asset Cache Not Updated on Other Cluster Members after Asset is updated on one cluster member (Doc ID 1536639.1)

Last updated on APRIL 03, 2024

Applies to:

Symptoms

After updating an asset on one cluster member, either via a publish to that cluster member or by directly edit/saving the asset,  the Asset Cache takes a while (e.g. a few minutes or longer) to update on the other members in the cluster.

The asset data appears correctly on the cluster member where the asset was updated, by other cluster members show the old asset data.

REST requests for assets return old data, as REST uses Asset Cache.

Changes

Cause

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