Selectors would work, but I recommend to avoid them - they can lead to confusion and problems. For example, adding consumers with selectors to a queue with a large backlog of messages means every one of those messages must be evaluated against the selector to see if it matches, hurting performance. Also, one question that comes up often on the boards - "I have unconsumed messages" - and selectors sometimes lead to this confusion.
For the Op -- is it possible to rework the solution to use two different queues? Queues are just that - a first-in, first-out structure for messages. If two sets of messages should not affect each other, then separate queues is likely the best approach. -- View this message in context: http://activemq.2283324.n4.nabble.com/consume-one-MessageGroup-by-several-consumers-tp4692555p4692580.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
