You have a forwarding bridge being established from machine #2 to machine #1; therefore, messages can only flow from #2 to #1. If you want messages to flow in both directions, either make it a 'duplex' bridge or create a forwarding bridge from #1 to #2.
Joe Get a free ActiveMQ user guide @ http://www.ttmsolutions.com Bastian Preindl wrote: > > 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 > this machine to the other one. 'cause it doesn't work from the other one > to this machine (whereas the output of the other one doesn't say anything > at all). > > Config file of machine #2 (belonging to the machine which establishes the > connection): > > <broker xmlns="http://activemq.apache.org/schema/core" > brokerName="localhost2" dataDirectory="${activemq.base}/data"> > > <transportConnectors> > <transportConnector uri="tcp://localhost:62002"/> > </transportConnectors> > > <networkConnectors> > <networkConnector uri="static:(tcp://localhost:62001)"/> > </networkConnectors> > > <persistenceAdapter> > <amqPersistenceAdapter syncOnWrite="false" > directory="${activemq.base}/data" maxFileLength="20 mb"/> > </persistenceAdapter> > > </broker> > > Config file of machine #1: > > <broker xmlns="http://activemq.apache.org/schema/core" > brokerName="localhost" dataDirectory="${activemq.base}/data"> > > <!-- Use the following to configure how ActiveMQ is exposed in JMX > --> > <managementContext> > <managementContext createConnector="false"/> > </managementContext> > > <persistenceAdapter> > <amqPersistenceAdapter syncOnWrite="false" > directory="${activemq.base}/data" maxFileLength="20 mb"/> > </persistenceAdapter> > > <!-- The transport connectors ActiveMQ will listen to --> > <transportConnectors> > <transportConnector name="openwire" > uri="tcp://localhost:62001" discoveryUri="multicast://default"/> > <transportConnector name="ssl" uri="ssl://localhost:61617"/> > <transportConnector name="stomp" > uri="stomp://localhost:61613"/> > <transportConnector name="xmpp" uri="xmpp://localhost:61222"/> > </transportConnectors> > > </broker> > > Machine #1 shall reliably forward all messages to machine #2, even if > broker #2 fails for some reason (then it should cache the messages until > #2 is back up again). > > Thanks a lot! > > Bastian > -- View this message in context: http://www.nabble.com/Broker-Clustering-tp19271212p19286772.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
