That looks like a bug.
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.
Thanks for the report.
----- Original Message -----
From: "Amin Abbaspour" <a.abbaspour(a)gmail.com>
To: infinispan-dev(a)lists.jboss.org
Sent: Saturday, January 16, 2010 3:03:54 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome /
Stockholm / Vienna
Subject: [infinispan-dev] Expiration does not work for Initially loaded Entries
Hi,
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.
Regards,
Amin
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev