Hi Ben,
your refactoring of LRUAlgorithm and related classes
has definitely solved this issue, good work!
Thanks,
-Uwe
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846351#3846351
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&m
Octopus, Ben,
using the most current sources from jboss-head and the posted testcase,
I can't find the described issue. I did a lot of testing,
but I am afraid - I cant help...
-Uwe
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846348#3846348
Reply to the
Hi,
I can easily reproduce the java.lang.OutOfMemoryError with the testcase,
but I am not sure - if this is really a bug.
Could it be possible, that simply the parameters in local-eviction-service.xml are not
optimal for the use case and the environment?
-uwe
View the original post :
http://w
I encounter the same problem, the exception for the no-existing node is raised again
and again.
Maybe the problem is again related to the Bug: [ 1013153 ] infinite loop in
LRUAlgorithm.prune
There has been a discussion about this, the related bug has been closed, but I see the
problematic code
Hi Ben,
a Unit Test is in work...
-uwe
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843617#3843617
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843617
---
This
I got the latest sources from CVS JBossCache1_0x and noticed following problem...
Our test is adding and removing nodes in the cache, now i got multiple times the
effect that LRUAlgorithm is processing a event - where the node referenced by the
event is no longer existing in cache.
A runtime ex
