There are 2-3 occurrences of the inherently racy get-or-test-and-set
antipattern to a ConcurrentMap. These should be replaced with the proper atomic
putIfAbsent loops.
Original issue reported on code.google.com by holger.h...@googlemail.com on 23 May 2011 at 10:01
Original issue reported on code.google.com by
holger.h...@googlemail.com
on 23 May 2011 at 10:01