e.g. in NodeMap it dosn't help that the method readerOwners() is synchronized, but the Collection (readOwnerList_) being returned by it being unsynchronized.
It wouldn't even help to make the IdentityLock.toString()-method synchronized, since the JVM's lock on the IdentityLock instance does not lock the NodeMap, which would be required to hinder the NodeMap's synchronized method's (which lock the NodeMap, but not it's instance-variables) to excecute and modify the concurrenty accessed readOwnerList_.... IMHO the only way to archive this is to use the synchronized version instead(created by java.util.Collection.synchronizedCollection(Collection)). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847730#3847730 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847730 ------------------------------------------------------- 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
