gaohoward, Thanks as always for your help. I don't think what you suggest is going to work because: 1. As soon as new messages get delivered to its local queue, it will stop sucking from other nodes. This is fine but it will mess up the delivery order of messages 2. If I turn on 'strict message ordering' presumably it will have to deliver everything to the one node? However, I found this FAQ which seems close to what I want: http://www.jboss.org/community/wiki/JBMHASingleton Unfortunately this FAQ does not work! Here are some of the problems: 1. There is no deploy/jboss-messaging.sar in JBoss 5.1.0.GA. I assume it is now called deploy/messaging? 2. deploy/messaging includes jms-ds.xml, which if you move into deploy-hasingleton then every cluster node except the primary will fail to start (citing 'DefaultJMSProvider not bound') All this was much easier under JBoss 4.2.3.GA. Under its all folder it already had most of JBoss MQ installed under deploy-hasingleton but it still had jms-ds.xml (actually hajndi-jms-ds.xml) under deploy. So I tried moving hajndi-jms-ds.xml from 4.2.3.GA to 5.1.0.GA, and it almost works but the 'server session pool for Message Driven Beans' bit fails to deploy. I tried deleting that and things start up, but the queues don't seem to pick up and begin processing messages after you bounce a cluster node. Please help! I just want JBoss Messaging to perform like JBoss MQ did: a single HA queue with load-balanced consumers. Richard. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240907#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...