I will go for active local queue (clustered/non-clustered) on the new node. (It is already done BTW) and I will change if someone come up with a valid point to change the implementation later. The HA for QueueBrowsers will just open a new browser on the new server and it will replace the objectID to match the new BrowserServerEndpoint. I had also to add the destination and the selector expression into BrowserState as I needed that information on the client to recreate the QueueBrowser on the new server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985470#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...