activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amok <>
Subject bridged brokers not doing their job
Date Tue, 23 Feb 2010 16:30:48 GMT

Hello everybody, 

I have a broker problem (no sh*t sherlock). 

the situation is as following (its a simplification of the reality): 

i have a machine that is a message producer. It produces on a topic called:
This backbone-proxy is configured to be producing at the following url:

Then there is the first broker. The first broker is watching this topic. The
configuration is as following: 


    <broker xmlns="" useJmx="true"
brokerName="localhost"  dataDirectory="data">

        <!-- Use the following to configure how ActiveMQ is exposed in JMX
            <managementContext createConnector="false"/>

            <amqPersistenceAdapter syncOnWrite="false" directory="data"
maxFileLength="20 mb"/>

        <!-- The transport connectors ActiveMQ will listen to -->
            <transportConnector name="openwire" uri="tcp://localhost:<port>"

                    <outboundTopicBridge localTopicName="backbone-proxy"
outboundTopicName="backbone" />

    <!-- JMS ConnectionFactory to use remote -->
    <bean id="remoteFactory"
        <property name="brokerURL"
value="failover:(tcp://myhostname:<port>)" />  

As you can see, i try to bridge the backbone-proxy to another remote topic,
named backbone. 

Then, as last, i have a consumer listening to the topic 'backbone'. 

This setup has worked before, so i know its not the bridge nor the
connection that is failing me. 

Ofcourse for this all to work, i need another broker running at the
following host: myhostname:<port>, the one that is looking after topic

it is this broker that has been changed and i can't figure out what has
happened. The configuration of that broker is as following: 


        The <broker> element is used to configure the ActiveMQ broker. 
    <broker xmlns=""
brokerName="testbroker" dataDirectory="/srv/dev/data/activemq"
            <managementContext createConnector="false"/>

            <kahaDB directory="someroot/activemq/kahadb"/>
            <transportConnector name="openwire" uri="tcp://<port>"/>


In these 2 examples, 'localhost' in the first hasn't been changed, and in the last example hasnt been changed. 

Very curious is the fact that when i change to localhost (as i
thought it would be) then i get connection problems coming from the consumer
i discussed above here. 

somebody said it was a network mask on the, but i really wonder how
that can be in a configuration file. 

Can somebody help me please? 

Thanks in advance, 

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message