[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-519 - Failover(HA) design discussion

Thu Oct 5 17:36:24 EDT 2006

anonymous wrote : 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".
  | 

When I said JBossConnection I meant somewhere on the structure of the connection. I didn' t mean to implement this state on JBossConnection. This will probably go into ConnectionState.

anonymous wrote : How do you envision this list to be initially populated. How it is kept in synch? 

At this point we have the list of available server at both PostOfficers (queue and topic).  AcceptView is populating the list. 
We will however need to decide how to communicate clients when a new node arrives on the cluster, but we can decide that later.

anonymous wrote : 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. 

Sounds good. I didn't like the idea of extending connection objects anyway.  Was just listing possibilities.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976425#3976425

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976425