I would quite appreciate any suggestions on using the
peer transport. Is it the right transport to bridge two
embedded brokers running on distinct servers?
Also, is it possible for me to programmatically alter the
peer broker's address?
Regards
/U
-- Original message
I think peer transport is just a shorthand for saying embedded broker +
multicast networking.
If you want finer grain of control in your peer brokers, you could
manually set it up with an embedded broker and just create multicast
transports and network connectors to it.
Hope this helps.
I am using AMQ4.1.
I have two JVM processes running (on different physical servers). I would
like each VM to have an embedded broker and yet connect to the peer VM's
embedded broker.
Finally, I would like subscribers on both the VMs to receive published messages
on the topic regardless of
