On 2/9/07, Adam Lally <[EMAIL PROTECTED]> wrote:
This dequeue method still seems fishy to me, even after your fix (not that your fix broke anything that wasn't already broken). Shouldn't there by a while (resource == null) instead of just an if? <snip/>
I forgot to tell you what class that method was in - it is in BoundedWorkQueue. The same situation occurs in CPECasPool.getCas(). In both cases the method is marked synchronized, so at first glance it looks like only one thread can be in there at at time. But since the method executes this.wait() I think this is not true, since a waiting thread releases its locks. -Adam
