"bwang00" wrote : Like Norbert mentioned, use tx now. There is a known problem in locking when tx is not used. We are fixing that in release 1.2. Do I need locking when I am "getting" a value that is already in a node's map? I do not care if other items are added to the map while I am "getting" this value do I? Is the issue you refer to the reason I am getting null?
"bwang00" wrote : If you are using TreeCacheAop, I'd suggest you try the latest pre-1.2 release in jboss-head. I have done some refactoring and bug fixing on the aop part. So far, when I am using the TreeCacheAop methods, I have not had any issues. This problem only occurs when using TreeCache's put/get methods. That said, would this refactoring be of any help? "bwang00" wrote : If you still are seeing the problem, the best way to help me out to troubleshoot is to write a JUnit test case. That can cut down the time that I need to generate one by myself. Besides, I can check in your test case in the src tree as well. I can try to create one, but this only seems to happen under high load (and with multiple nodes), and then, it does not happen everytime. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856640#3856640 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856640 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
