[
https://issues.apache.org/jira/browse/AMQ-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020933#comment-15020933
]
Tim Boven commented on AMQ-5582:
--------------------------------
I see no indication whatsoever that activemq isn't following the specs - it's
following the specs rather well and "using" the spec to even support additional
things that are not possible (or difficult) with the spec.
The "issue" will with messages in a queue and using a message selector exists
in every messaging system I know.
I however see a possible feature request related to the virtual topic concept.
As ActiveMQ implements this by a topic that directly forwards its messages to
queue's, it's logically that these messages stay on the queue's but what if we
make it possible to e.g. define a selector for the forwarding from the topic to
the queue in the ActiveMQ config - or even better take the given selector from
the client and use that one to filter the messages coming from the topic onto
the queue (assuming that the selector will be the same for all clients)
> 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
> Priority: Blocker
>
> 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)
