[
https://issues.jboss.org/browse/ISPN-10074?page=com.atlassian.jira.plugin...
]
Dan Berindei commented on ISPN-10074:
-------------------------------------
Will clarified that this is expected behaviour: because we don't want entries to
disappear in one cache iteration and reappear in a later iteration, entries which should
be expired according to maxidle are returned until a read operation or the purge worker
thread removes them.
However, this is only implemented in the segmented data container implementations. We need
to modify the non-segmented implementations to also ignore entries expired only because of
maxidle.
DefaultSegmentedDataContainer executeTask() and iterator() include
expired entries
----------------------------------------------------------------------------------
Key: ISPN-10074
URL:
https://issues.jboss.org/browse/ISPN-10074
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 10.0.0.Beta2, 9.4.10.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Major
Fix For: 10.0.0.Beta3, 9.4.11.Final
The {{executeTask()}} javadoc doesn't mention expired entries, but
{{iterator()}}'s says they shouldn't be included, and non-segmented containers do
not include them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)