Thanks for the explanation,
my workaround is to have only one consumer without selector and delegate
accordingly in the onMessage() method.
I was just wondering whether this behaviour is done-by-design or should
potentially work.
Br, A.
--
Sent from: http://activemq.2283324.n4.nabble.com/Act
Hi
Could I suggest you use a JMS topic, which each of the consumers being a
durable shared consumer where you use a separate consumer subscription for each
filter.
The issue I think you are hitting is that with a JMS Queue the is only a one
core created and with message groups per group only o
Dear experts,
Assume you have a JMS queue Q with two consumers A and B using message
selectors.
A listens on messages having country='US'.
B listens on messages having country='Canada'.
A producer C sents subsequently messages to Q with either country='US' or
country='Canada' as property and a m
