"Tim Fox" wrote : I don't understand why you need a new method on the post office (the bind with the node id), can you shed some light....? | | On failover, it's the post office that will detect the failure using JGroups, so it will know what has failed over. I'm doing the failover from client side. The client will detect the socket failure and it will open a new connection on a new server, when the connection is opened the original nodeID is also sent then the queue from the old server is made active on the current server. "Tim Fox" wrote : Therefore all it needs to do, is for each of the remote queue stubs correspsonding to the queues for which it will take over responsiblity it needs to replace them with a local clustered queue and call load() on it. Consider the case where the client also died with the server, for example a MessageDrivenBean located on the save VM as the JMS Server. On that case all we have to do is to wait the client come back alive, we don't need to failover that queue. Why I'm saying that? Because I think it would make sense to fail over as it's needed, having the client taking the action on where to fail over to. I'm just prototyping at this point. At this point I'm having to deal with PostOffice interface as well because in a failover event, non clustered queues will be reconnected as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980408#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...