[
https://issues.apache.org/jira/browse/JCS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840341#comment-15840341
]
Thomas Vandahl commented on JCS-172:
------------------------------------
As you can configure the implementation to use for ElementAttributes, you may
roll your own as a workaround. Like so:
{code:title=MyElementAttributes.java|borderStyle=solid}
/**
* @see java.lang.Object#clone()
*/
@Override
public IElementAttributes clone()
{
ElementAttributes c = (ElementAttributes) super.clone();
c.setCreateTime();
return c;
}
{code}
> 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
> Assignee: Thomas Vandahl
> Fix For: jcs-2.1
>
> 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)
