Hello,
The problem came back again even after setting the queue size to 500,000.
I can't just ignore this problem because it just takes too much cpu.
I have a question regarding the way the eviction work. I thought that the
problem happens maybe because of the way I evict my objects and for some reason
the cache thinks that the object was revisited and therefor adds it again to
the cache. This is what I do in my eviction listener :
public void logNodeEvent(NodeEvent ne) {
Fqn fqnActionFather = ...
// handling evicition of nodes according to the object type
if (ne.getType().name().equals("NODE_EVICTED")) {
if (ne.getFqn().size() > 0) {
if (ne.getFqn().isChildOf(fqnActionFather )) {
String id= (String)
ne.getFqn().getLastElement();
Node node = ne.getCache().getNode(ne.getFqn());
if (node != null) {
Action action = (Action) node.get(id);
// handle eviction
}
.
.
.
.
Thanks for the help,
Elad.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172135#4172135
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172135
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
