[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9003: ------------------------------------ You didn't mention it, so I wasn't 100% sure you'd want to keep running it, and whether it would do the same thing on all the owners. I was thinking about the node where the entries are written. And I trust you about the iterator, but if there's a store on the source node, the state provider will call {{DataContainer.containsKey()}}, which may or may not refresh the entry (javadoc doesn't say anything about it). {{maxIdle}} works based on reads, not just writes, and the difference between reads on the primary and the backups can be just as big as {{maxIdle}} is. That's why I said we'd need to update the last-access timestamp on the primary after running the algorithm (and on the backups as well, if the backups can also trigger clustered {{maxIdle}} expiration). -- This message was sent by Atlassian JIRA (v7.5.0#75005)