You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/02/12 15:53:11 UTC

[jira] [Commented] (AMQ-5582) Queues stop sending to consumers after a threshold

    [ https://issues.apache.org/jira/browse/AMQ-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318304#comment-14318304 ] 

Timothy Bish commented on AMQ-5582:
-----------------------------------

This is expected behavior.  You can work around it a bit by increasing the maxPageSize value to hold more messages in memory but if you continue to produce to the Queue and only consume a small number it will occur again.  One the memory cache fills dispatch will stop until you start consuming those messages or you set a TTL and they start expiring.  

> Queues stop sending to consumers after a threshold
> --------------------------------------------------
>
>                 Key: AMQ-5582
>                 URL: https://issues.apache.org/jira/browse/AMQ-5582
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.10.0
>            Reporter: Krishna
>
> If a consumer of a queue is consuming based on a selector after about 500 messages the queue stops sending any message to the consumer (even matching messages).
> I have a standalone test case here. The test case by default uses a VirtualTopic changing it to a queue will exhibit the problem as well.
> https://bitbucket.org/calvinkrishy/camel-jms-test
> Discussion in the mailing list:
> http://activemq.2283324.n4.nabble.com/Consumer-queues-of-virtual-topic-and-the-web-console-td4689995.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)