[concurrency-interest] LinkedBlockingDeque deadlock? (original) (raw)

Martin Buchholz martinrb at google.com
Wed Jul 8 00:05:44 UTC 2009

[+core-libs-dev]

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: http://cr.openjdk.java.net/~martin/webrevs/openjdk7/BlockingQueue/

Martin

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? Thanks, Ariel Weisberg

Concurrency-interest mailing list Concurrency-interest at cs.oswego.edu http://cs.oswego.edu/mailman/listinfo/concurrency-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.openjdk.java.net/pipermail/core-libs-dev/attachments/20090707/5854e79b/attachment.html>

More information about the core-libs-dev mailing list