As you know, JBM 1.4 contains message redistribution with clustered queues. This means, if you have a clustered queue over several nodes in a cluster, and consumers on one node are faster than consumers on another node, then messages will be pulled from one node to another transparently to satisfy demand. The idea here is it should give optimal use of server resources for processing messages. Problem is this behaviour can confuse users. The classic case is they set up a cluster of N nodes with a clustered queue, send messages to a single node and wonder why all their consumers on different nodes aren't processing the messages. This is because the local node still has spare cpu cycles so there is no point in allowing other nodes to consume, since that would involve unnecessary network round tripping. So it's actually the optimal use of resources. Regarding JBM 2.0 I'd appreciate any feedback on whether you think this feature is of value. Or the customer confusion value outweighs its value, or if you think it should behave in some other way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170708#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...