To acheive the split between "high priority" and "low priority" without starving the low-priority messages, I recommend:
1. use separate queues to split the priorities 2. either use dedicated consumers for the low priorities that do not take resources away from the higher priorities, or use some form of simple heuristic to choose when to process the same (e.g. after processing 10 high-priority messages, process 1 low-priority message) The use of a heuristic will be important to allow the balance between starving low-priority messages and delaying high-priority ones. Messaging features, such as priority queueing, are limited and not likely to give you the desired results. BTW, I may have missed it - why use message groups? Is messaging order important? -- View this message in context: http://activemq.2283324.n4.nabble.com/Selective-consuming-of-priority-messages-with-message-groups-tp4704813p4704938.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
