ActiveMQ network of brokers increased latency

Question

I have configured an ActiveMQ network of brokers, which seems to work fine, function wise.
However, the capacity of messages traveling from a producer which is connectes to broker a, to a consumer which is connected to broker b, is about three times worse, then for producer/consumer connected to the same broker.
This seems odd to me, as I was under the impression that once broker a, passes the message to broker b, it is a delivered message (from broker a POV), so there should be no capacity decrease.

here is my activemq.xml configuration:

<beans
  xmlns="http://www.springframework.org/schema/beans"
  xmlns:amq="http://activemq.apache.org/schema/core"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

<broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true" persistent="false">

    <destinationPolicy>
        <policyMap>
          <policyEntries>
            <policyEntry topic=">" producerFlowControl="true" memoryLimit="5mb">
              <pendingSubscriberPolicy>
                <vmCursor />
              </pendingSubscriberPolicy>
            </policyEntry>
            <policyEntry queue=">" producerFlowControl="true" memoryLimit="50mb">

              <!-- Use VM cursor for better latency
                   For more information, see:

                   http://activemq.apache.org/message-cursors.html

              <pendingQueuePolicy>
                <vmQueueCursor/>
              </pendingQueuePolicy>
              -->
            </policyEntry>
          </policyEntries>
        </policyMap>
    </destinationPolicy> 





    <!-- 
        The managementContext is used to configure how ActiveMQ is exposed in 
        JMX. By default, ActiveMQ uses the MBean server that is started by 
        the JVM. For more information, see: 

        http://activemq.apache.org/jmx.html 
    -->
    <managementContext>
        <managementContext createConnector="false"/>
    </managementContext>

    <networkConnectors>
        <networkConnector name="tomer-amq-test1" uri="static:(tcp://tomer-amq-test1:61616)" networkTTL="3"/>
    </networkConnectors>


    <!-- 
        Configure message persistence for the broker. The default persistence
        mechanism is the KahaDB store (identified by the kahaDB tag). 
        For more information, see: 

        http://activemq.apache.org/persistence.html 
    -->
    <persistenceAdapter>
        <kahaDB directory="${activemq.base}/data/kahadb"/>
    </persistenceAdapter>


      <!--
        The systemUsage controls the maximum amount of space the broker will 
        use before slowing down producers. For more information, see:

        http://activemq.apache.org/producer-flow-control.html

    <systemUsage>
        <systemUsage>
            <memoryUsage>
                <memoryUsage limit="500 mb"/>
            </memoryUsage>
            <storeUsage>
                <storeUsage limit="1 gb"/>
            </storeUsage>
            <tempUsage>
                <tempUsage limit="500 mb"/>
            </tempUsage>
        </systemUsage>
    </systemUsage>
    -->


    <!-- 
        The transport connectors expose ActiveMQ over a given protocol to
        clients and other brokers. For more information, see: 

        http://activemq.apache.org/configuring-transports.html 
    -->
    <transportConnectors>
        <transportConnector name="tomer-amq-test2" uri="tcp://0.0.0.0:61616"/>
    </transportConnectors>

</broker>

<!-- 
    Enable web consoles, REST and Ajax APIs and demos

    Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details 
-->
<import resource="jetty.xml"/>

</beans>

Am I wrong?
Is there some special configuration I have to employ?
can someone shed some light on the flow?

Tx Tomer

Answer 1

It seems that running in debug, will slow down the servers a lot more when a message is transfered to a diffrent broker, then when it is sent to a consumer, hence the capacity problem.
Once I set log level to info, the capacity of both solutions seems the same.