"clebert.suconic(a)jboss.com" wrote : I have *tried* to drive fail over from client side. | | Last week I could make a state transfer from one node to another, moving all the messages from a failed queue to a new queue. | As already discussed, moving messages is not an option since there may be 10s of millions of messages in each partial queue. Also fully client driven failover won't work since we need to ensure JMS semantics with durable subscriptions - especially when doing in memory persistent message replication - this we have already discussed too. "Clebert" wrote : | There are implications of doing this way as we will could have more than one Local Queues when a failover occurs. | | Say if you have two nodes A and B, each node with a client and a durable subscription on that client. | | Now say if node A fails. Now the clients from node A will be redirect into node B, and Routers will have to treat B's connections as they were still on nodeA but now they are local on node B. | Why is this a problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980934#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...