I'm evaluating infinispan 4.1.0.BETA2 to ensure that JBoss Cache cans be replaced with Infinispan in my product. During my study, I've noticed that the parameter maxEntries is strangely managed by the Eviction Algorithms, I don't know if it is a bug so I prefer to ask first but it looks like it. I expect that the cache size never exceeds the maximum amount of entries after the eviction thread woke up however according to the following Unit Test, it doesn't seem to be true. See the code below:
Is-it normal? If so how can we know the effective value of the max entries?
Thank you in advance for your answers,
Ce message a été modifié par: Nicolas Filotto