[concurrency-interest] LinkedBlockingDeque deadlock?

David Holmes davidcholmes at aapt.net.au
Tue Jul 7 19:14:19 EDT 2009


The poll()ing thread is blocked waiting for the internal lock, but there's
no indication of any thread owning that lock. You're using an OpenJDK 6
build ... can you try JDK7 ?

I don't recall anything similar to this, but I don't know what version that
OpenJDK6 build relates to.

Make sure you haven't missed any exceptions occurring in other threads.

David Holmes

> -----Original Message-----
> From: concurrency-interest-bounces at cs.oswego.edu
> [mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of Ariel
> Weisberg
> Sent: Wednesday, 8 July 2009 8:31 AM
> To: concurrency-interest at cs.oswego.edu
> Subject: [concurrency-interest] LinkedBlockingDeque deadlock?
> 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

More information about the Concurrency-interest mailing list