[infinispan-issues] [JBoss JIRA] Commented: (ISPN-336) Entries loaded via loadAll not being checked for expiration
[
https://jira.jboss.org/jira/browse/ISPN-336?page=com.atlassian.jira.plugi...
]
Manik Surtani commented on ISPN-336:
------------------------------------
I have added a test to BaseCacheStoreFunctionalTest (extended by all the CacheStore impls
we ship) which proves that expiry information attached to entries survives cache restarts
(i.e., after being preloaded using loadAll()).
http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/test/java/org/i...
And they all pass. So I haven't been able to prove this as a bug. Closing, please
reopen if you can prove this.
Entries loaded via loadAll not being checked for expiration
-----------------------------------------------------------
Key: ISPN-336
URL: https://jira.jboss.org/jira/browse/ISPN-336
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 4.0.0.CR3
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.GA
Those keys loaded initially from CacheLoader via loadAll method do not obey expiration
rules unless they are modified. Just after first change they expire following lifespan and
maxIdle values.
It's interesting that we do check for expiration in some cases such as
BucketBasedCacheStore when loading an individual. We should probably do it regardless of
the type of cache loader used. IOW, we should probably move the check to
CacheLoaderInterceptor or similar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira