[concurrency-interest] Propagation of signals to non-interrupted thread

Martin Buchholz martinrb at google.com
Sun Nov 13 22:30:32 EST 2011

The propagation here is nothing to do with poorly written code but a
> work-around for lack of detail in the spec prior to JDK 5 that allowed an
> interrupted thread to consume a notification.

I rediscovered this spec:

      * <p>An implementation can favor responding to an interrupt over
     * method return in response to a signal. In that case the
     * must ensure that the signal is redirected to another waiting thread,
     * there is one.

but this is an "Implementation Consideration" and it could be clearer that
a thread returning abnormally from await cannot cause a lost signal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20111113/f49d2e4e/attachment.html>

More information about the Concurrency-interest mailing list