[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-318) CacheLoader persistent item should have an age limit

Manik Surtani (JIRA) jira-events at lists.jboss.org
Tue Sep 18 10:25:11 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBCACHE-318?page=all ]

Manik Surtani closed JBCACHE-318.
---------------------------------

    Fix Version/s:     (was: 2.1.0.GA)
       Resolution: Rejected

Agree that this should not be a part of the cache loader.  Use your own external loop with a time stamp element in the node to clear out expired items.

> CacheLoader persistent item should have an age limit
> ----------------------------------------------------
>
>                 Key: JBCACHE-318
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-318
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ben Wang
>         Assigned To: Manik Surtani
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Currently items that are persisted has no notion of age out. So let's say it is fairly common in SFSB to have the state not live more than 2 weeks in the store, for example. The other usage is when the cache crashed and the persistent store won't get cleaned up even when the items are orphaned.
> Bela refused to put this functionality in the cache loader layer. So Manik's idea is to wrap around the object in the CacheStoreInterceptor with an additional timestamp. This way an offline thread can come in and clean them.
> We can also check how does the current SFSB does this?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list