[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:
------------------------------------
According to the reporter this has to do with preload, which is surprising. Preload code
(currently) does:
try {
state = loader.loadAll();
} catch (CacheLoaderException e) {
throw new CacheException("Unable to preload!", e);
}
for (InternalCacheEntry e : state)
cache.getAdvancedCache().withFlags(SKIP_CACHE_STATUS_CHECK).put(e.getKey(),
e.getValue(), e.getLifespan(), MILLISECONDS, e.getMaxIdle(), MILLISECONDS);
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