I'd just like to say that I believe David is exactly right here. I've been following (or rather trying and failing most of the time) the javaMemoryModel (http://www.cs.umd.edu/~pugh/java/memoryModel/) mailing list, and this kind of issue is very difficult to analyse correctly.
My advice, FWIW, is to stop messing around and just use util.concurrent by Doug Lea (http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html). There aren't many people who can prove that their tricky concurrent Java code is correct, but Doug Lea can. Just use EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap and sleep at night. Toby. On Thu, Feb 13, 2003 at 02:14:28PM -0500, David Jencks wrote: > I think the jboss code has the same problem as double checked locking -- > described by Joshua Bloch as "wildly counterintuitive". > > ... > > I don't think localMap has a accurate view of clients unless this is > synchronized. Just as with double-checked locking, it can read a partially > initialized version of clients. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development