Expiring elements after restarting cache

tugman Apr 13, 2008 7:41 PM

Hello.

I'm using FileCacheLoader to store elements of cache in disk and LRU eviction policy. If I put a node in cache, after "timeToLiveSeconds" passed, it is removed (and my listener gets called). This is ok.

My problem is that when I restart de cache, elements that are stored there are reloaded, but never more get expired and stay there forever. I think they should expire not just because maxNodes were reached; after restart, "TimeToLiveSeconds" should work for elements loaded from disk like it was before restarting.

Is there a way to have this behaviour ?

Thanks in advance.

1. Re: Expiring elements after restarting cache

manik Apr 14, 2008 7:56 PM (in response to tugman)

It should evict stuff that has been reloaded as well. Do you only see this problem with the FCL, or with other cache loaders as well? Do you have a unit test that recreates this?
Actions
2. Re: Expiring elements after restarting cache

tugman Apr 15, 2008 5:31 AM (in response to tugman)

I only use it with FCL, so I don't know what's the behaviour with other CLs.

I have a small java program that recreates it, I don't have a JUnit, for example. Do you want me to send it ?
Actions
3. Re: Expiring elements after restarting cache

manik Apr 22, 2008 3:56 AM (in response to tugman)

Yes please. I would prefer it if you could rewrite it as a TestNG unit test though, and demonstrate that it does in fact fail on the src tree of the JBoss Cache version you're referring to. :-)
Actions

Go to original post