[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-519 - Failover(HA) design discussion
by clebert.suconic@jboss.com
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
19 years, 6 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-519 - Failover(HA) design discussion
by ovidiu.feodorov@jboss.com
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#3976420
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976420
19 years, 6 months
[Other JBoss Development Design] - Re: run.sh to launch JBoss in background
by mazz@jboss.com
I don't know why the loop :-) I was assuming the server would exit specifically with a code of 10 as a way for it to indicate it wants to be "rebooted" immediately. I don't know if it ever does, but why that loop if not for the ability for the server to say it wants to be restarted upon exit? Just a guess.
But for 100% backward compatibility, I just left it as is so the script would do exactly what it did before if that LAUNCH_IN_BACKGROUND var isn't set. I have no problems with taking that loop out:
| if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
| "$JAVA" $JAVA_OPTS \
| -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
| -classpath "$JBOSS_CLASSPATH" \
| org.jboss.Main "$@"
| else
| "$JAVA" $JAVA_OPTS \
| -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
| -classpath "$JBOSS_CLASSPATH" \
| org.jboss.Main "$@" &
| JBOSS_PID=$!
| export JBOSS_PID
| fi
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976400#3976400
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976400
19 years, 6 months