[concurrency-interest] spurious wakeups semantics

Rémi Forax forax at univ-mlv.fr
Wed Nov 2 14:34:39 EST 2005

Brian Goetz a écrit :
> - This can happen whenever a single wait set is used for multiple 
> conditions.  Until Java 5, this was the _only_ way to get multiple 
> conditions on a single condition queue, and you still can't with 
> intrinsic condition queues.  So what should we do?  Outlaw bounded 
> buffers, and other concurrent objects which require more than one 
> condition?
> - This can happen whenever notifyAll is used to wake up more than one 
> thread, even if all threads are waiting for the same condition.  There 
> are good engineering reasons why you might prefer notifyAll to single 
> notify.

what are these good engineering reasons ?
and are these reasons can be applied to Condition.signal/signalAll too
in case of fair Lock ?

> These cases don't describe "sloppiness", they describe sensible 
> practices for common real-world problems.


> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at altair.cs.oswego.edu
> http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest

Rémi Forax

More information about the Concurrency-interest mailing list