-
Bug
-
Resolution: Done
-
Critical
-
24.0.0.Final
-
None
-
Workaround Exists
-
-
Undefined
Currently, Infinispan's expiration reaper is only enabled if the cache specifies a non-zero lifespan or maxIdle. However, given that lifespan and maxIdle can be specified per entry, users that utilize these methods can experience a memory leak, due to the reaper not running. Rather, we should enable the expiration reaper if a non-zero wakeup interval is specified.
We can then update our default configurations to disable the expiration reaper where appropriate.