Hi, It seems odd that your networkConnector config is connecting to itself. So you use this config
server1 config <networkConnector name="jms1" uri="static://(tcp://172.16.1.x2:61616)" networkTTL="2" failover="true"> server2 config <networkConnector name="jms2" uri="static://(tcp://172.16.1.x1:61616)" networkTTL="2" failover="true"/> rather than the one you were using. The networkTTL specifies how many brokers the messages and subscriptions can pass through. If it still doesnt work, make the networkTTL value larger. More info http://activemq.org/site/networks-of-brokers.html here , on network connector properties. Regards, Marlon devu wrote: > > Hi, I have some problem to do it like this: > > I have two jms servers. > producer A connect to jms1, consumer B connect jms1 to listen topic1, > consumer C connect to jms2 topic2. > > Then producer start a session and two topics in different queues. However, > consumer C could not receive topic2 from jms2. It has to connect to jms1 > to receive them. > > I already config two jms servers like this: > > <networkConnector name="jms1" > uri="static://(tcp://172.16.1.x1:61616,tcp://172.16.1.x2:61616)" > failover="true"> > > <networkConnector name="jms2" > uri="static://(tcp://172.16.1.x1:61616,tcp://172.16.1.x2:61616)" > failover="true"/> > > the ip address 172.16.1.x1 is the first jms ip address and 172.16.1.x2 is > the second one. > > > > > > > > -- View this message in context: http://www.nabble.com/replicate-messages-tf3022632.html#a8402879 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
