Tweet
As an alterantive to JCS' internal remote cache invalidation via LTCP connected auxiliary caches, a event based remote cache invalidation mechanism based on Hazelcast distributed topics was implemented. See http://oxpedia.org/wiki/index.php?title=Running_a_cluster#Remote_Cache_Inv alidation for details.
Therefore, the following configuration parameter is added to the file 'cache.properties':
# Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false'
# to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'.
com.openexchange.caching.jcs.eventInvalidation=tru e
Therefore, the following configuration parameter is added to the file 'cache.properties':
# Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false'
# to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'.
com.openexchange.caching.jcs.eventInvalidation=tru e