"clebert.suconic(a)jboss.com" wrote : | Wouldn't a queue.load take care of this? Maybe I didn't understand your point here. If you have 2 nodes, node A and node B. There exists durable sub S1 on node A for topic T Messages are being sent via node A to topic T. They are routed to node B where they go into S1. node B then fails More messages are now sent to node A, it is a requirement of the JMS spec that S1 still receives the messages sent. If you don't reload S1 until the client requests it, then S1 won't get the message and we have broken the JMS spec. This isn't such an issue when using a shared db since we persist before send, but when doing in memory replication it simply won't work. A similar reasoning applies to queues. We're not permitted to lose any messages destined for a queue while failover is occurring. We must ensure that all messages end up in the queue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980440#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...