Tweet
Only IDLE timeout for non-volatile cache elements to reduce high-cost select-for-update SQL queries
To accomplish that the 'cache.ccf' file has been changed in the way that there is no more a "hard" timeout for following cached elements: context, user, user configuration
Those elements now only have a idle timeout. Meaning if frequently accessed, they stay in cache. If not accessed since a certain amount of time, they encounter a idle timeout and thus are removed from cache.
The following properties were changed in file 'cache.ccf':
jcs.region.Context.elementattributes.MaxLifeSecond s=-1
jcs.region.User.elementattributes.MaxLifeSeconds=-1
jcs.region.UserConfiguration.elementattributes.Max LifeSeconds=-1
To accomplish that the 'cache.ccf' file has been changed in the way that there is no more a "hard" timeout for following cached elements: context, user, user configuration
Those elements now only have a idle timeout. Meaning if frequently accessed, they stay in cache. If not accessed since a certain amount of time, they encounter a idle timeout and thus are removed from cache.
The following properties were changed in file 'cache.ccf':
jcs.region.Context.elementattributes.MaxLifeSecond s=-1
jcs.region.User.elementattributes.MaxLifeSeconds=-1
jcs.region.UserConfiguration.elementattributes.Max LifeSeconds=-1