"clebert.suconic(a)jboss.com" wrote : | 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. | How can you ensure that different clients that use the same queue fail over on to the same node? There are other issues here. When a durable subscription is attached to a topic, then the subscription must retain all messages *even if it isn't active* - this is a requirement of the JMS spec. If you only load the durable sub when requested to by a client, then you're going to lose when doing in memory persistent replication. A similar reasonsing applies to queues. anonymous wrote : | 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. Non clustered queues don't need to be reconnected. If queues want to benefit from HA then they should be made clustered. Personally I don't think you can drive the failover fully from the client side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980416#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...