Are the JMSXGroups required because messages need to be processed in order?
If not, remove the JMSXGroups and let messages distribute across the consumers. If ordering is an issue, then it may be necessary to look outside of ActiveMQ to fully solve the problem. For example, it would be straight-forward to write a camel server that routes between one incoming queue and multiple consumer-specific queues using whatever logic you prefer. Of course, you could also consider adding a feature to ActiveMQ and contributing it to the community! That section of code looks straight-forward enough to modify. By the way, is a network of brokers in use? Things get more complicated in that case. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-policy-for-ActiveMQ-with-new-message-groups-tp4687812p4687861.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
