[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-336) Entries loaded via loadAll not being checked for expiration

[Manik Surtani (JIRA)]

     [ https://jira.jboss.org/jira/browse/ISPN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani resolved ISPN-336.
--------------------------------

    Fix Version/s:     (was: 4.0.0.GA)
       Resolution: Cannot Reproduce Bug


> 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
>
> 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