Hi,
apparently my mistake was to copy and paste the configuration from one
broker to the others and not change the broker's name ('localhost'). But I
wonder why this doesn't lead to problems from the beginning but as recently
as I add the second durable subscriber to a broker having the same name
Hi
I'm extending my network brokers from two (forwarding bridge A->B) to three
and I've established the following connections via forwarding bridges:
A->B
A->C
B->C
whereas C is new in the network of brokers. Now I've one topic where I'd
like B and C to be a durable subscriber with different me
Hi,
thanks a lot for both the hint and the link - it works perfectly now!
Bastian
--
View this message in context:
http://www.nabble.com/Broker-Clustering-tp19271212p19307785.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Great,
it works that way. Now only the persistency problem is left. Broker #1
receives a bunch of messages from a producer, but Broker #2 is currently
unavailable. How can I achieve that Broker #2 keeps the messages until #2 is
back up and sends it then (and even keep them persistent if itself go
Hi,
on one of the both machines (config file follows) it states:
INFO DemandForwardingBridge - Network connection between
vm://localhost2#24 and tcp://localhost/127.0.0.1:62001(localhost) has been
established.
The question is if messages are exchanged in both directions or only from
th
Hi,
thanks for the quick answers.
Joe Fernandez wrote:
>
> Can you confirm that a forwarding bridge has been established between the
> producing and consuming brokers?
>
No, not yet. Do I need something additional like Camel to establish this?
Regards
Bastian
--
View this message in conte
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 c
