ActiveMQ Invalid content was found starting with element

在配置mirroredQueue的时候，destinationInterceptors标签提示Invalid content was found starting with element。

解决方案：

ActiveMQ在5.4之后，解析xml是按照字母排序解析的“alpahbetical ordering”。

只要把destinationInterceptors放到正确的位置，就可正确启动。

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --><!-- START SNIPPET: example --><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"><!-- Allows us to use system properties as variables in this configuration file --><beanclass="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"><property name="locations"><value>file:${activemq.base}/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="localhost" dataDirectory="${activemq.base}/data"destroyApplicationContextOnStop="true" useMirroredQueues="true"><!-- 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 --><destinationInterceptors><virtualDestinationInterceptor><virtualDestinations><compositeQueue name="TestQueue"><forwardTo><filteredDestination selector="odd = 'yes'" queue="TestQueue2" /><!--<filteredDestination selector="i = 5" topic="BAR"/> --></forwardTo></compositeQueue></virtualDestinations></virtualDestinationInterceptor></destinationInterceptors><destinationPolicy><policyMap><policyEntries><policyEntry topic=">" producerFlowControl="true"memoryLimit="1mb"><pendingSubscriberPolicy><vmCursor /></pendingSubscriberPolicy></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> --></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="${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="20 mb"/> </memoryUsage> <storeUsage> <storeUsage limit="1 gb"/> </storeUsage> <tempUsage> <tempUsage limit="100 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="openwire" uri="tcp://0.0.0.0:61616" /></transportConnectors></broker><!-- Enable web consoles, REST and Ajax APIs and demos It also includes Camel (with its web console), see ${ACTIVEMQ_HOME}/conf/camel.xml for more info Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details --><import resource="jetty.xml" /></beans><!-- END SNIPPET: example -->