I certainly appreciate your trying to keep me happy, as that is the prime objective. Perhaps you could speak to my wife about that. And in all seriousness, I do appreciate the time you have spent. Requiring the producer of the messages to be cognizant of how many nodes are in the cluster in order to distribute them round robin is IMHO not a very good solution. Any process producing messages to a clustered queue should not care how many nodes are in the queue. Furthermore, absent any configuration (MsgSelector, priority etc;) to the contrary, messages should get consumed in the order they were produced. That just makes sense. It's called a Queue. It should act like a queue. To have a queue, that has multiple consumers, have the messages pulled off it in a haphazard order just doesn't make sense to me. If I am waiting in line (i.e. the queue for our english friends) for a teller at the bank I don't want to see someone (say, the manager) grabbing anyone in the line to go to the next available teller. I would expect that the person who has been in line the longest (i.e. the front of the line) gets the next available teller. Now of course if I was at the Movies it would be different. There, when I go to get some snacks there are six registers and six lines and I have to pick the line I want. If I get in the shortest line and then the person in front of me has a big order and I end up standing there while the other longer lines go faster, well then I get pissed. I much prefer the single line feeding into all six registers so the person who was there first gets serviced first, regardless of which register it is. Get my drift? :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144648#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...