Question

我已经配置了一个ActiveMQ经纪人网络，这似乎工作正常，功能明智但是，从连接到经纪人a的生产者传递到连接到经纪人b的消费者的消息的容量大约是连接到同一经纪人的生产者/消费者的三倍。这对我来说似乎很奇怪，因为我的印象是，一旦经纪人a将消息传递给经纪人b，它就是一个传递的消息（来自经纪人POV），所以不应该减少容量。

这是我的activemq.xml配置：

<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>

我错了吗？我必须采用一些特殊配置吗？
有人可以对流量有所了解吗？

的Tx Tomer的

Answer 1

似乎在调试中运行会在将消息转移到不同的代理时将服务器放慢速度，然后将消息发送给消费者，从而导致容量问题。一旦我将日志级别设置为info，两种解决方案的容量似乎都相同。

ActiveMQ经纪人网络增加了延迟

1 个答案: