I went ahead and created a ticket as well:
https://issues.apache.org/jira/browse/AMQ-5582
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-queues-of-virtual-topic-and-the-web-console-tp4689995p4691427.html
Sent from the ActiveMQ - User mailing list archive at Nab
tbain98 wrote
> And what's your expect behavior for the messages that don't match the
> filter for your consumer? What do you anticipate happening to them with
> this configuration?
Since the messages I send are non-persistent I would expect the
messages that do not match the selector to stay in
tbain98 wrote
> OK, so I finally got around to looking at your producer and consumer code
> in BitBucket. So it looks like you're intentionally only consuming half
> the messages you produce; is that right? If so, to what end? You never
> mentioned this particular characteristic of your test; an
I made the virtual topic selectorAware and the problem went away. All
messages are received by the consumer without much delays.
I was able to reproduce this only with queues as well. That is the messages
were sent to and consumed from a queue based on a selector. After a while
the consumer seemed
I am able to reproduce this consistently. Messages don't arrive at the
consumer of the virtual topic queue.
I have a simple test case in this maven project:
https://bitbucket.org/calvinkrishy/camel-jms-test
One should be able to run it with mvn camel:run. The test uses 5.10.0 as an
embedded broke
We are using the stock ActiveMQ 5.10.0 configuration (with minor
modifications for JMX). With this configuration we have run into a very
strange issue every now and then with messages not being dispatched from the
consumer queues of a virtual topic until we click 'browse' on the web
console of that
