[
https://issues.apache.org/jira/browse/AMQ-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef reopened AMQ-5582:
--------------------------------
Assignee: Arthur Naseef
I'm sorry -- this is expected state of operation? Really?
I know selectors tend to be problematic, but until we put a big notice on the
front ActiveMQ page that states this limitation exists and will not be fixed,
this is not an acceptable response.
The JMS specification does not state that selectors only work with small limits
on numbers of pending messages. Therefore, ActiveMQ stating it supports the
JMS specification is misleading.
> 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
> Assignee: Arthur Naseef
>
> 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)
