Release 6.20.0: Increased idle timeout and avoiding infinite put-remove cycle

[changerequest]

Increased idle timeout for cached objects to be greater than default web UI refresh period. Thus frequently accessed objects (especially context instances) are ensured to stay in cache.

Moreover the IssueRemoveOnPut is set to false to avoid possible infinite put-remove cycles between remote Open-Xchange hosts.

These changes are accomplished in cache.ccf file through:

jcs.region.User.cacheattributes.MaxMemoryIdleTimeS econds=360
jcs.region.User.elementattributes.IdleTime=360

jcs.region.UserConfiguration.cacheattributes.MaxMe moryIdleTimeSeconds=360
jcs.region.UserConfiguration.elementattributes.Idl eTime=360

jcs.region.Context.cacheattributes.MaxMemoryIdleTi meSeconds=360
jcs.region.Context.elementattributes.IdleTime=360

jcs.auxiliary.LTCP.attributes.IssueRemoveOnPut=fal se