ActiveMQ队列消息过期时间设置和自动清除解决方案

版本 apache-activemq-5.15.3

1、消息过期设置

参数详情

1）message过期则客户端不能接收

2）ttlCeiling：表示过期时间上限（程序写的过期时间不能超过此时间，超过则以此时间为准）

3）zeroExpirationOverride：表示过期时间（给未分配过期时间的消息分配过期时间）

配置示例

 <broker>





     ...





     <plugins>





         <!-- 86,400,000ms = 1 day -->





         <timeStampingBrokerPluginttlCeiling="30000" zeroExpirationOverride="30000" />





     </plugins>





     ...





 </broker>

2、死信队列设置

消息过期后会进入死信队列，如不想抛弃死信队列，默认进入ACTIVEMQ.DLQ队列，且不会自动清除；对于过期的消息进入死信队列还有一些可选的策略:放入各自的死信通道、保存在一个共享的队列（默认），且可以设置是否将过期消息放入队列的开关以及死信队列消息过期时间。

1）直接抛弃死信队列

AcitveMQ提供了一个便捷的插件：DiscardingDLQBrokerPlugin，来抛弃DeadLetter。如果开发者不需要关心DeadLetter，可以使用此策略。

配置示例

<broker>





...





<plugins>





    <!-- 丢弃所有死信-->





    <discardingDLQBrokerPlugindropAll="true"  dropTemporaryTopics="true" dropTemporaryQueues="true" />





    <!-- 丢弃指定死信-->





    <!-- <discardingDLQBrokerPlugindropOnly="MY.EXAMPLE.TOPIC.29 MY.EXAMPLE.QUEUE.87" reportInterval="1000" />-->





    <!--使用丢弃正则匹配到死信-->





    <!--<discardingDLQBrokerPlugindropOnly="MY.EXAMPLE.TOPIC.[0-9]{3} MY.EXAMPLE.QUEUE.[0-9]{3}" reportInterval="3000"/>-->





    </plugins>





    ...





 </broker>

2）定时抛弃死信队列

默认情况下，ActiveMQ永远不会过期发送到DLQ的消息。但是，从ActiveMQ 5.12开始，deadLetterStrategy支持expiration属性，其值以毫秒为单位。

配置示例

<policyEntryqueue=">"…>





...





<deadLetterStrategy>





    <sharedDeadLetterStrategy processExpired="true" expiration="30000"/>





</deadLetterStrategy>





   ...





</policyEntry>

3、慢消费者策略设置

Broker将会启动一个后台线程用来检测所有的慢速消费者，并定期关闭关闭它们;中断慢速消费者，慢速消费将会被关闭。abortConnection是否关闭连接;如果慢速消费者最后一个ACK距离现在的时间间隔超过阀maxTimeSinceLastAck，则中断慢速消费者。

配置示例

<policyEntryqueue=">"…>





     …





    <slowConsumerStrategy>





        <abortSlowConsumerStrategyabortConnection="false"/>  <!--不关闭底层链接-->





    </slowConsumerStrategy>





    …





</policyEntry>

4、测试

1）配置activemq.xml；

2）批量消息发送；

3）等待若干秒，消息减少；

4）等待若干秒，消息队列清除（设置了抛弃死信队列）；

5）等待若干秒，消息队列清除（未设置抛弃死信队列，设置了死信队列过期时间）；

6）等待若干秒，消息队列清除（不抛弃死信队列，死信队列不过期）；

5、参考网址

https://my.oschina.net/coderedrain/blog/724943?utm_source=tuicool&utm_medium=referral

http://ask.csdn.net/questions/376817

http://activemq.apache.org/message-redelivery-and-dlq-handling.html

完整配置

<!--





    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:xsi="http://www.w3.org/2001/XMLSchema-instance"





  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>





 





   <!-- Allows accessing the server log -->





    <bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"





          lazy-init="false" scope="singleton"





          init-method="start" destroy-method="stop">





    </bean>





 





    <!--





        The <broker> element is used to configure the ActiveMQ broker.





    -->





    <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" schedulePeriodForDestinationPurge="10000">





        <destinationPolicy>





            <policyMap>





              <policyEntries>





			  <policyEntry queue=">" gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000">





				<deadLetterStrategy>





					<sharedDeadLetterStrategy processExpired="true"  expiration="30000"/>





				</deadLetterStrategy>





			  </policyEntry>





                <policyEntry topic=">" >





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





              </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.data}/kahadb"/>





        </persistenceAdapter>





          <!--





            The systemUsage controls the maximum amount of space the broker will





            use before disabling caching and/or slowing down producers. For more information, see:





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





          -->





          <systemUsage>





            <systemUsage>





                <memoryUsage>





                    <memoryUsage percentOfJvmHeap="70" />





                </memoryUsage>





                <storeUsage>





                    <storeUsage limit="100 gb"/>





                </storeUsage>





                <tempUsage>





                    <tempUsage limit="50 gb"/>





                </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&wireFormat.maxFrameSize=104857600"/>





            <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>





            <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>





            <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>





            <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>





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





		





        <plugins>





            <!-- 86,400,000ms = 1 day -->





            <timeStampingBrokerPlugin ttlCeiling="30000"      zeroExpirationOverride="30000" />





            <!-- <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true" />-->





        </plugins>





    </broker>





 





    <!--





        Enable web consoles, REST and Ajax APIs and demos





        The web consoles requires by default login, you can disable this in the jetty.xml file





        Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details





    -->





    <import resource="jetty.xml"/>





</beans>





<!-- END SNIPPET: example -->