[jira] Commented: (QPID-607) Dispatcher threads do not die

["Robert Greig (JIRA)" <qp...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529547 ] 

Robert Greig commented on QPID-607:
-----------------------------------

Committed to M2 branch.

Looking at the code it *should* be handled by interrupts but clearly there is at least one case where this does not happen.

> Dispatcher threads do not die
> -----------------------------
>
>                 Key: QPID-607
>                 URL: https://issues.apache.org/jira/browse/QPID-607
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2
>         Environment: Any
>            Reporter: Robert Greig
>            Assignee: Robert Greig
>
> During extensive testing we see many (e.g. hundreds) of threads running with the following stack:
> "Dispatcher-Channel-1" daemon prio=1 tid=0x00002aab004e6530 nid=0x5d24
> waiting on condition [0x0000000052978000..0x0000000052978c00]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1767)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at org.apache.qpid.client.util.FlowControllingBlockingQueue.take(FlowControllingBlockingQueue.java:74)
>        at org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:2680)
> This is because the dispatcher does a blocking take, rather than a poll with a timeout.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.