Message groups force processing of a single destination to only one consumer at a time - not really the processing model you've described.
If there were separate queues for each device, message groups would work. However, if there are large numbers of devices, that could be a real concern since it would mean large numbers of destinations. Using camel, it would be possible to route to specific instances of the consumer application (engine) by having each engine listen on a queue dedicated to it, then having a camel component that decides which engine will process which device and route to that engine. On top of that, it would be possible to have 2 instances of the engine listening on each queue, using JMSXGroup's, to ensure high availability and redundancy. Just a thought... -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-Group-tp4680478p4680479.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
