[concurrency-interest] ArrayBlockingQueue (and possibly others) not waking on interrupt?

Martin Buchholz martinrb at google.com
Mon Dec 1 15:02:46 EST 2014


On Mon, Dec 1, 2014 at 11:50 AM, Charles Oliver Nutter
<headius at headius.com> wrote:
> I'm working to narrow that down now. You're right...I don't expect to
> have found a bug, but I'm having trouble explaining the behavior I'm
> seeing.
>
> Just to clarify the key point, though: LockSupport.park should be 100%
> wakeable using Thread#interrupt, yes? There's no situation where a
> thread in park would *not* be expected to wake up in response to
> Thread#interrupt?

Right - park() is allowed to return spuriously, but not allowed to
spuriously fail to return !
But these methods are usually called in a loop, and if a caller failed
to check or notice the interrupt then it would call park again.


More information about the Concurrency-interest mailing list