Hi Tim, Thanks a lot for the reply and the suggestions. Please find some of my comments inline.
Regards, Frankie Tim Bain wrote > First, shouldn't you be expecting thread 2 to consume message 1? > > [Frankie] The thread numbers were symbolic only. In real life the numbers > would be something like Thread #11 and Thread #19. What I meant was that > whichever thread is consuming from the second route will consume the > messages 1 and 3. > > Second, I'm guessing you're defining the routes in an XML file, in which > case don't you need to encode "<" as "<" and ">" as ">"? > > [Frankie] The routes are defined through the Java code, by using "<" and > ">" instead of "<" and ">" > > Third, use a JMX viewer such as JConsole to look at the subscriptions on > that queue. Find the subscription that isn't working (#1) and see whether > it's present and whether its selector looks correct. See whether any > messages have been dispatched to it. > > [Frankie] Will try that. > > Fourth, use the web console to browse the queue. Look at the message that > isn't getting consumed and see if the headers look correct. > > [Frankie] Checked the web console for the local AMQ broker and the message > remained sitting on the queue. Will re-check how the headers are looking, > even though not sure why it wouldn't work because it's explicitly set in a > same way as it is for low priority messages. > > Tim -- View this message in context: http://activemq.2283324.n4.nabble.com/Selective-consuming-of-priority-messages-with-message-groups-tp4704813p4704818.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
