[jira] Commented: (QPID-659) Messages sent to a queue that uses selectors may cause high CPU load.

["Martin Ritchie (JIRA)" <qp...@incubator.apache.org>]

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

Martin Ritchie commented on QPID-659:
-------------------------------------

Due to the use of a pre-delivery queue a message that is not desired by any consumer will stick in the queue. This will then cause the async delivery process to loop consuming a large amount of CPU. The async process will not stop because there are 'message on the queue' and 'active consumers'. 

Using the management console to pop the top message or connecting a consumer that doesn't use selectors will allow the async process to terminate.

> Messages sent to a queue that uses selectors may cause high CPU load.
> ---------------------------------------------------------------------
>
>                 Key: QPID-659
>                 URL: https://issues.apache.org/jira/browse/QPID-659
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2
>            Reporter: Martin Ritchie
>             Fix For: M2.1
>
>
> If a message that doesn't match a the consumers selector arrives on the queue the asynchronous delivery manager will not terminate.

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