both of those options are largely the same. The idea of duplex is that a spoke broker only needs to know about a hub broker to get a bidirectional networks and a single connection is shared for forwarding in either direction. When there is a firewall in between, only one port needs to be opened so duplex is easier to configure in this case.
With each configuring a static networkconnector to the other, there are two unidirectional network connections. On 7 September 2011 10:28, dcheckoway <dchecko...@gmail.com> wrote: > Hello, > > I'd like your advice on setting up a simple 2-node network of brokers. I > will have both consumers & producers each connected to one of the nodes > (randomly), and I'd like messages to flow to any consumer connected to > either node. > > Assume "node1" and "node2" are the hostnames, and consumers and producers > will connect with: > failover:(tcp://node1:61616,tcp://node2:61616)?randomize=true > > I'm wondering which of the following configurations would be "preferred", if > there are any advantages or disadvantages to either: > > === Option 1: only one node specifically configured for network, i.e. > > node1 is set up with no networkConnector, just a stock out-of-the-box, > otherwise standalone broker. > node2 is set up with: > <networkConnector uri="static:(tcp://node1:61616)" duplex="true"/> > > === Option 2: both nodes aware of each other, i.e. > > node1 is set up with: > <networkConnector uri="static:(tcp://node2:61616)"/> > node2 is set up with: > <networkConnector uri="static:(tcp://node1:61616)"/> > > Any advice on this? I want to make sure I understand the purpose of > "duplex". If my suggestions above imply that I'm clueless about it, please > clue me in... :-) > > Thanks! > > ----- > Dan Checkoway > dcheckoway gmail com > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Preferred-config-for-2-node-network-of-brokers-tp3795676p3795676.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://fusesource.com http://blog.garytully.com
