activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Broker Clustering
Date Tue, 02 Sep 2008 14:35:11 GMT
2008/9/2 Bastian Preindl <bastian.preindl@joinvision.com>:
>
> Hi,
>
> I'd like to interconnect two servers with a broker on each server. Messages
> sent to the first broker shall be replicated on (or forwarded to) the second
> broker. The communication is one way only. If one of the both brokers fail
> for some reason, the messages should be sent/received after the connection
> is re-established. The consumers/producers should only need to connect to
> the local broker.
> Future brokers should be able to be connected to the first broker.
>
> For now I've created a topic with a durable subscriber and it works perfect
> for one broker. But I'm pretty much overstrained by all the possibilities
> given for the interconnection of multiple brokers. I've tried to
> interconnect two brokers using a "networkConnector" (using tcp) but if a
> topic is created on the first broker, and a consumer is subscribing on the
> second broker, messages aren't delivered at all.
>
> For my pretty simple scenario, what would be the best solution/method
> (having extensibility in mind)?

For clustering, you use Master/Slave...
http://activemq.apache.org/masterslave.html

(not store and forward networks).

You're main choice is between using a shared file system or database -
for easy fail-back and management - or to use pure master slave which
only supports failover, not fail-back and you have to manually copy
around files if you want to bring back an old master.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

Mime
View raw message