btw: this is not just an issue of debugging - other methods like the various 'printInfo()' (even in TreeCache()) eventually throwsConcurrentModificationException when being called while the cache is in use.
If we want to keep the underlying Collections unsynchronized for performance-reasons, we must never pass references to them. methods like 'LockMap.readerOwners()' are a 'must not' in respect to concurrency. I guess all the synchronizing must be carefully reviewed before this may go gold. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847734#3847734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847734 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
