What you may want instead is the staticallyIncludedDestinations
feature. You could also use startup destinations.
In either case it won't match what you want since you're using
queues. If you really want both A's consumers and B's consumers to
receive the same set of messages, then you'll need to use a topic,
and perhaps something like virtual destinations to bridge to a queue
at each broker. Otherwise queue semantics hold even across the network.
It sounds like you may want to try out the master/slave feature
instead if you care about both 0 message loss during failure and that
a message must be consumed once and only once.
John
On Dec 28, 2006, at 7:32 AM, activemqer wrote:
Hi,
I'm trying to cluster two brokers on two separate machines. I'd
like to post
messages to broker A and the messages to flow to broker B so I have
two
brokers with same set of messages. I'd like this to be able to
failover from
one broker to the other in case of an outage.
The problem is I don't see the messages flow between the two
brokers, they
stay in the broker A's persistant storage. I found in the
documentation that
there is a way to enforce the message flow with the dynamicOnly set
to false
but it did not make any difference. Am I missing anything?
I have the following network connectors configured:
* on host A:
<networkConnector name="A and B" uri="static://(tcp://B:61616)"
failover="true" dynamicOnly="false" networkTTL="10"/>
* on host B:
<networkConnector name="A and B" uri="static://(tcp://A:61616)"
failover="true" dynamicOnly="false" networkTTL="10"/>
One more detail, if it helps, when I'm posting messages to the
queue, there
are no listeners on either broker.
Thanks.
--
View this message in context: http://www.nabble.com/network-of-
brokers-tf2890777.html#a8076003
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
