[
https://issues.jboss.org/browse/ISPN-7146?page=com.atlassian.jira.plugin....
] 
Vladimir Dzhuvinov edited comment on ISPN-7146 at 3/30/19 3:35 AM:
-------------------------------------------------------------------
The issue is still present in 9.4.11.Final.
According to the config schema docs and JavaDocs -1 is still given as the value to disable
the thread:
_interval	long	60000	Interval (in milliseconds) between subsequent runs to purge expired
entries from memory and any cache stores. If you wish to disable the periodic eviction
process altogether, set interval to -1._
When checking the XML config for `interval="-1"` programmatically Infinispan
returns 60000:
{{Configuration.expiration().wakeUpInterval()}}
was (Author: vdzhuvinov):
The issue is still present in 9.4.11.Final.
According to the config schema docs and JavaDocs -1 is still given as the value to disable
the thread:
_interval	long	60000	Interval (in milliseconds) between subsequent runs to purge expired
entries from memory and any cache stores. If you wish to disable the periodic eviction
process altogether, set interval to -1._
 Expiration interval set to -1 behaves incorrectly
 -------------------------------------------------
                 Key: ISPN-7146
                 URL: 
https://issues.jboss.org/browse/ISPN-7146
             Project: Infinispan
          Issue Type: Bug
          Components: Core
    Affects Versions: 8.2.4.Final
            Reporter: Vladimir Dzhuvinov
            Assignee: Will Burns
            Priority: Major
 According to the guide and XML docs <expiration interval="-1"/> disables
the expiration thread. But it doesn't, and expiration proceeds to run every 1 minute
(which is the default behaviour when the expiration setting is omitted).
 Later I found that it takes <expiration interval="0"/> to disable the
expiration thread. 
--
This message was sent by Atlassian Jira
(v7.12.1#712002)