ActiveMQ的spring配置文件

从官网copy出来，做了部分修改：

 <?xml version="1.0" encoding="UTF-8"?>
 <beans xmlns="http://www.springframework.org/schema/beans"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:amq="http://activemq.apache.org/schema/core"
         xsi:schemaLocation="http://www.springframework.org/schema/beans
         http://www.springframework.org/schema/beans/spring-beans.xsd
         http://activemq.apache.org/schema/core
         http://activemq.apache.org/schema/core/activemq-core.xsd">

 <!-- Allows us to use system properties as variables in this configuration file -->
 <!-- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
     <property name="locations">
         <value>file:${activemq.conf}/credentials.properties</value>
     </property>
 </bean> -->
 <!--
     The <broker> element is used to configure the ActiveMQ broker.
 -->
 <broker xmlns="http://activemq.apache.org/schema/core" brokerName="zhang" dataDirectory=".">
     <!--
             For better performances use VM cursor and small memory limit.
             For more information, see:

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

             Also, if your producer is "hanging", it's probably due to producer flow control.
             For more information, see:
             http://activemq.apache.org/producer-flow-control.html
     -->
     <destinationPolicy>
         <policyMap>
             <policyEntries>
                 <policyEntry topic=">" producerFlowControl="true">
                     <!-- The constantPendingMessageLimitStrategy is used to prevent
                          slow topic consumers to block producers and affect other consumers
                          by limiting the number of messages that are retained
                          For more information, see:

                          http://activemq.apache.org/slow-consumer-handling.html

                     -->
                     <pendingMessageLimitStrategy>
                         <constantPendingMessageLimitStrategy limit="1000"/>
                     </pendingMessageLimitStrategy>
                 </policyEntry>
                 <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
                 <!-- Use VM cursor for better latency
                        For more information, see:

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

                   <pendingQueuePolicy>
                     <vmQueueCursor/>
                   </pendingQueuePolicy>
                   -->
                       <deadLetterStrategy>
                           <individualDeadLetterStrategy queuePrefix="TEST"/>
                     </deadLetterStrategy>
                     <pendingQueuePolicy>
                         <storeCursor/>
                     </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>
     <!--
         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="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
     If using ActiveMQ embedded - the following limits could safely be used:

     <systemUsage>
         <systemUsage>
             <memoryUsage>

                 <memoryUsage limit="20 mb"/>
             </memoryUsage>
             <storeUsage>
                 <storeUsage limit="1 gb"/>
             </storeUsage>
             <tempUsage>
                 <tempUsage limit="100 mb"/>
             </tempUsage>
         </systemUsage>
     </systemUsage>
     -->
     <systemUsage>
         <systemUsage>
             <memoryUsage>
                 <memoryUsage limit="1 mb"/>
             </memoryUsage>
             <storeUsage>
                 <storeUsage limit="32 mb"/>
             </storeUsage>
             <tempUsage>
                 <tempUsage limit="32 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>
     <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
         <transportConnector name="openwire"
         uri="tcp://0.0.0.0:61616?maximumConnections=1000"/>
         <transportConnector name="amqp"
         uri="amqp://0.0.0.0:5672?maximumConnections=1000"/>
     </transportConnectors>
     <!-- destroy the spring context on shutdown to stop jetty -->
     <shutdownHooks>
         <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook"/>
     </shutdownHooks>
 </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>

关于通配符的说明（http://activemq.apache.org/wildcards.html）：

. is used to separate names in a path
* is used to match any name in a path
> is used to recursively match any destination starting from this name