[JCS-172] MaxLife element attribute causing cache region to stop responding

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: jcs-2.0-beta-2, jcs-2.0
• Fix Version/s: jcs-2.1
• Assignee: Thomas Vandahl
• Reporter: Tom Schroeder
• Created: 23/Jan/17 16:16
• Updated: 14/Jun/20 16:07
• Resolved: 26/Jan/17 20:04

Description

We are using a cache region to stage some content, and have been using the MaxLife attribute to expire content after a certain amount of time. This seemed to work when using the jcs-2.0-beta-1 version. However, after upgrading our project to either the jcs-2.0-beta-2 or the jcs-2.0 versions, our staging cache seems to stop retaining content after the system has been up for the MaxLife time. After that is seems that any content placed in our stagedContent region is immediately expired. Placing an item in the cache with a CacheAccess.put() and then immediately trying to retrieve it with a CacheAccess.get() returns null. I have attached a copy of our cache configuration file for reference.