Cache invalidation is broken during edits of repository data having distributed cache mode (Doc ID 1037811.1)

Last updated on MARCH 11, 2015

Applies to:

Oracle ATG Web Commerce - Version 2006.3 and later
Information in this document applies to any platform.
A repository component may have its autoUpdateSubscribers property set to true by default. When this property is "true", the repository will add rows to the DAS_GSA_SUBSCRIBER table on startup and remove the rows on shutdown.
The rows in the DAS_GSA_SUBSCRIBER table contain hostname and port details that ATG uses to open socket connections that allow ATG instances to exchange cache coordination signals between server instances.
The <item-descriptor> tag in the repository's XML template may have the cache-mode attribute set to distributed


Edits of profile data in Commerce Service Center (CSC)  never cause updated items to be dropped from repository cache on Production servers if distributed cache mode is in use by the data. Site users continue to see stale, cached values until repository cache is dropped manually.
The repositories running on a CSC instance never have rows added to the DAS_GSA_SUBSCRIBER table on the Production schema for its item descriptors that use distributed cache mode.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms