"Tim" wrote : How can you ensure that different clients that use the same queue fail over on to the same node? Based on what we talked before, a client connection to a nodeA will always have to faile to a nodeB. A server rule will determine this. "Tim" wrote : Non clustered queues don't need to be reconnected. If queues want to benefit from HA then they should be made clustered. What we should do then if a connectionState has a non clustered queue on its hierarchy during a connection failure event then? Throw an exception? Disconnect the Consumer? So far I think we could (don't know if we should) reconnect non clustered topics on the new node. We won't be able to guarantee deliveries, but at least we wouldn't interrupt the client. Now if the requirement is to fail over only on ClusteredQueues we should know what to do then. "Tim" wrote : Personally I don't think you can drive the failover fully from the client side. I will be able to refactor anything if we get some problem. I'm constructing this piece by piece, we will be able to refactor later. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980431#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...