[
https://jira.jboss.org/jira/browse/JBCACHE-1576?page=com.atlassian.jira.p...
]
Dennis Reed updated JBCACHE-1576:
---------------------------------
Summary: Incorrect handling of eviction maxNodes=0/-1 in JBC 3 (was: Incorrect
handling of eviction maxNodes=0 in JBC 3)
Incorrect handling of eviction maxNodes=0/-1 in JBC 3
-----------------------------------------------------
Key: JBCACHE-1576
URL:
https://jira.jboss.org/jira/browse/JBCACHE-1576
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Eviction
Affects Versions: 3.2.2.GA
Reporter: Dennis Reed
Assignee: Dennis Reed
JBCACHE-1274 was not fully implemented, missing a few key changes:
ExpirationAlgorithm with maxNodes=-1 incorrectly logs a warning of too many nodes (after
JBCACHE-1574)
FIFOAlgorithm treats maxNodes=0 as unlimited and -1 as 0
LFUAlgorithm javadocs say maxNodes=0 is unlimited
LRUAlgorithm treats maxNodes=0 as unlimited
MRUAlgorithm treats maxNodes=-1 as 0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira