[
https://issues.apache.org/jira/browse/JCS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840213#comment-15840213
]
Tom Schroeder commented on JCS-172:
-----------------------------------
In talking with Thomas Vandahl on the commons user list, I believe this issue
is fixed in the latest trunk for commons-jcs-core-2.1-SNAPSHOT. The relevant
SVN commit info is:
Version: 1779938
Time: 1/23/17, 9:54AM
Commit Message: Fix creation time not updating during clone()
I built the latest jar from the trunk source and the problem we were seeing
goes away. Thanks a lot!
> MaxLife element attribute causing cache region to stop responding
> -----------------------------------------------------------------
>
> Key: JCS-172
> URL: https://issues.apache.org/jira/browse/JCS-172
> Project: Commons JCS
> Issue Type: Bug
> Affects Versions: jcs-2.0-beta-2, jcs-2.0
> Reporter: Tom Schroeder
> Attachments: cache.ccf
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
