The quotes that follow are from the HA Design document (http://wiki.jboss.org/wiki/Wiki.jsp?page=NewMessagingHADesign) Clebert wrote : | The idea is to have JBossConnection knowing the current state of subscriptions, producers and listeners. | Could you please qualify this a little bit more? The state of consumer/producers, as well as the state of their parent session and connection is maintained by their corresponding client-side delegates, as well as their server-side endpoints. So I don't exactly understand what you are trying to say with "have JBossConnection knowing the current state of subscriptions, producers and listeners". Clebert wrote : | JBossConnection (or an extension of that class) will have a list of other servers to be connected in case of failure. | How do you envision this list to be initially populated. How it is kept in synch? Clebert wrote : | One point we are leaving opened at this point is how to recover redeliviries of eventual already received messages. | Are you talking about persistent or non-persistent messages here? Clebert wrote : | JBossConnectionHA will be responsible for capturing creation events, storing then in a list and recreate its delegates when a Connection (RemotingConnection) is failed. | How about we don't have any JBossConnectionHA? A JBossConnection is "failover enabled" or not, depending on whether the "FailoverAspect" or "ClusterAspect" is present in its aspect stack or not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976420#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...