Cache Validation

In certain circumstances, the Content Store's internal caches can be updated with an outdated copy of an object, resulting in stale content in the caches. You can prevent this problem ever arising by setting a configuration property called validateObjectsAfterInsert. Setting this property to true causes the Content Engine to validate all newly-cached items with the database, thereby ensuring that the caches will never contain stale information. The property is set to false by default, since database validation of every cache insertion is a potentially time-consuming operation and may have a significant effect on performance. You can, however, set the property if the possibility of stale content appearing in the caches is unacceptable.

To set this property, add configuration-layer-root/io/api/CacheManager.properties to one of your configuration layers and include the required setting in the file:

validateObjectsAfterInsert=true