Can you guys try it one more time by getting the latest jboss-head? It is actually not a serious error, per se. Here is why.
What happened was in TreeCache, it will do another nodeModified event notification after the parent (leaf node has no problem) node is evicted. So you see, it will loop back to eviction policy again. And therefore could not found the evicted node. Bela and I have found a solution to stop the notification in this case. So the problem should be solved. If not, it is something else I need to look at. Thanks, -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846028#3846028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3846028 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
