No network of brokers. The JMSXGroupID is being used to block concurrent execution of the task. Concurrent execution would cause one process to basically trash what the other one is doing as well as present many opportunities for failure.
Your idea about a camel route/server to route the message is actually similar to another idea I had. I was hoping there was some magic we could find in ActiveMq that we weren't aware. Thanks again for your response. I will take a look at the code. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-policy-for-ActiveMQ-with-new-message-groups-tp4687812p4687863.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
