You are correct. The high level todo list is: (1) Cluster the topics. Should be easy as this is just done with a broadcast call. (2) Cluster the StateManager. So that state of a user connection is maintained accross all of the MQ nodes. (3) Cluster the queues. Harder problem as you want to avoid the synchronization hotspot that can occur when multiple nodes are tring to compete for messages from one destination. (3) Provide a fail-over Peristence Manager. If the PM of one node dies, all the nodes in the cluster should be able to switch to the backup PM.
Regards, Hiram >From: Peter Antman <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default >jbossmq-se rvice.xml >Date: Fri, 9 Nov 2001 15:42:22 +0100 (CET) > >On 9 Nov, Hiram Chirino wrote: > > > > Yes. This peice of the puzzle should let us transparently switch over >to > > another MQ node server if the first one we were connected with dies. >But > > note that there's many other things todo before we have truly >'clustered' > > JBossMQ. > >So there is basically no "clustering" of the destinations? > >To get HA in this environment we would have the "publisher" connect to >the same node as the "subscibers" and when that node goes down both >publisher and subscribers must find the same available node to connect >to? Have I got it? > >//Peter > > > > Regards, > > Hiram > > > >>From: Peter Antman <[EMAIL PROTECTED]> > >>To: [EMAIL PROTECTED] > >>CC: [EMAIL PROTECTED] > >>Subject: Re: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default > >>jbossmq-se rvice.xml > >>Date: Fri, 9 Nov 2001 09:14:39 +0100 (CET) > >> > >>Hiram, I am jumping up and down here in excitement. Is this really what > >>it look like: a first cut of a clustered JBossMQ? Tell me its true. > >> > >>//Peter > >> > >>On 8 Nov, Hiram Chirino wrote: > >> > User: chirino > >> > Date: 01/11/08 22:26:37 > >> > > >> > Modified: src/etc/conf/default jbossmq-service.xml > >> > Log: > >> > Created a new JBossMQ IL that uses the HA framework. > >> > > >> > Revision Changes Path > >> > 1.8 +15 -2 >jbossmq/src/etc/conf/default/jbossmq-service.xml > >> > > >> > Index: jbossmq-service.xml > >> > =================================================================== > >> > RCS file: > >>/cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v > >> > retrieving revision 1.7 > >> > retrieving revision 1.8 > >> > diff -u -r1.7 -r1.8 > >> > --- jbossmq-service.xml 2001/10/28 01:27:00 1.7 > >> > +++ jbossmq-service.xml 2001/11/09 06:26:37 1.8 > >> > @@ -7,7 +7,7 @@ > >> > <!-- > >> --> > >> > <!-- > >>===================================================================== >--> > >> > > >> > -<!-- $Id: jbossmq-service.xml,v 1.7 2001/10/28 01:27:00 chirino >Exp $ > >>--> > >> > +<!-- $Id: jbossmq-service.xml,v 1.8 2001/11/09 06:26:37 chirino >Exp $ > >>--> > >> > > >> > <!-- > >> > | This is where you can add and configure your MBeans. > >> > @@ -26,7 +26,9 @@ > >> > <depends>JBOSS-SYSTEM:service=Naming</depends> > >> > > >> > <classpath archives=" > >> > - jbossmq.jar > >> > + jbossmq.jar, > >> > + jbossmqha.jar, > >> > + jbossha.jar > >> > "/> > >> > > >> > <!-- > >>==================================================================== --> > >> > @@ -100,6 +102,17 @@ > >> > <attribute name="ServerBindPort">8091</attribute> > >> > <attribute name="PingPeriod">60000</attribute> > >> > </mbean> > >> > + > >> > +<!-- This will start a High Availability (HA) connection factory > >>(experimental) --> > >> > +<!-- > >> > + <mbean code="org.jboss.mq.il.ha.HAServerILService" > >> > + name="JBossMQ:service=InvocationLayer,type=HA"> > >> > + <attribute > >>name="ConnectionFactoryJNDIRef">HAConnectionFactory</attribute> > >> > + <attribute > >>name="XAConnectionFactoryJNDIRef">HAXAConnectionFactory</attribute> > >> > + <attribute name="PartitionName">DefaultPartition</attribute> > >> > + <attribute > >>>name="LoadBalancePolicy">org.jboss.ha.framework.interfaces.FirstAvailable</attribute> > >> > + </mbean> > >> > +--> > >> > > >> > <!-- > >> > | The following three line create 3 topics named: > >> > > >> > > >> > > >> > > >> > _______________________________________________ > >> > Jboss-development mailing list > >> > [EMAIL PROTECTED] > >> > https://lists.sourceforge.net/lists/listinfo/jboss-development > >> > >>-- > >>Jobba hos oss: http://www.tim.se/weblab > >>------------------------------------------------------------ > >>Peter Antman Technology in Media, Box 34105 100 26 Stockholm > >>Systems Architect WWW: http://www.tim.se > >>Email: [EMAIL PROTECTED] WWW: http://www.backsource.org > >>Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 > >>------------------------------------------------------------ > >> > >> > >>_______________________________________________ > >>Jboss-development mailing list > >>[EMAIL PROTECTED] > >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at >http://explorer.msn.com/intl.asp > >-- >Jobba hos oss: http://www.tim.se/weblab >------------------------------------------------------------ >Peter Antman Technology in Media, Box 34105 100 26 Stockholm >Systems Architect WWW: http://www.tim.se >Email: [EMAIL PROTECTED] WWW: http://www.backsource.org >Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 >------------------------------------------------------------ > > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
