[concurrency-interest] LinkedBlockingDeque deadlock?
martinrb at google.com
Tue Jul 7 17:05:44 PDT 2009
Doug Lea and I are (slowly) working on a new version of LinkedBlockingDeque.
I was not aware of a deadlock but can vaguely imagine how it might happen.
A small reproducible test case from you would be useful.
Unfinished work in progress can be found here:
On Tue, Jul 7, 2009 at 15:30, Ariel Weisberg <ariel at weisberg.ws> wrote:
> Hi all,
> I did a search on LinkedBlockingDeque and didn't find anything similar
> to what I am seeing. Attached is the stack trace from an application
> that is deadlocked with three threads waiting for 0x00002aaab3e91080
> (threads "ExecutionSite: 26", "ExecutionSite:27", and "Network
> Selector"). The execution sites are attempting to offer results to the
> deque and the network thread is trying to poll for them using the
> non-blocking version of poll. I am seeing the network thread never
> return from poll (straight poll()). Do my eyes deceive me?
> Ariel Weisberg
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the core-libs-dev