Ami, Well the nice thing about ActiveMQ is almost everything is configurable. >From your description I gather you have a requirement for high availability. If this is the only reason for using multiple brokers then using a master-slave would be simplify things for you.
http://activemq.apache.org/shared-file-system-master-slave.html Clark www.ttmsolutions.com ActiveMQ reference guide at http://bit.ly/AMQRefGuide ami.rozen wrote: > > Hi > We are using the activemq brokers in a high scale production environment. > To prevent downtime we decided to configure the brokers to work as a > network of brokers. > There are 2 brokers which use a fixed list of urls to connect to each > other. > The clients and services use the failover url with a list of the available > brokers. > Currently we have 2 clients that connect to the brokers and we saw (in the > brokers UI) that the messages aren't distributed in an even way. > 1) Is this ok ? > 2) is there a configuration to distribute the messages evenly between the > brokers ? > 3) Is there an additional configuration which can bust the performance ? > We don't mind losing messages if one of the brokers is down. > > The configuration we are using in the broker xml file is: > <networkConnectors> > <networkConnector name="default-dev13" > uri="static://(tcp://host_name:61616)"/> > </networkConnectors> > <!-- The transport connectors ActiveMQ will listen to --> > <transportConnectors> > <transportConnector name="openwire" > uri="tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=100&jms.useAsyncSend=true&wireFormat.maxInactivityDuration=0"/> > <transportConnector name="ssl" uri="ssl://localhost:61617"/> > <transportConnector name="stomp" > uri="stomp://localhost:61613"/> > <transportConnector name="xmpp" uri="xmpp://localhost:61222"/> > </transportConnectors> > Thank you > Ami > > -- View this message in context: http://old.nabble.com/network-of-brokers-question-tp29020595p29027874.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
