ActiveMQ队列消息过期时间设置和自动清除解决方案
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
ActiveMQ队列消息过期时间设置和⾃动清除解决⽅案
版本 apache--5.15.3
1、消息过期设置
参数详情
1)message过期则客户端不能接收
2)ttlCeiling:表⽰过期时间上限(程序写的过期时间不能超过此时间,超过则以此时间为准)
3)zeroExpirationOverride:表⽰过期时间(给未分配过期时间的消息分配过期时间)
配置⽰例
1. <broker>
2. ...
3. <plugins>
4. <!-- 86,400,000ms = 1 day -->
5. <timeStampingBrokerPluginttlCeiling="30000" zeroExpirationOverride="30000" />
6. </plugins>
7. ...
8. </broker>
2、死信队列设置
消息过期后会进⼊死信队列,如不想抛弃死信队列,默认进⼊ACTIVEMQ.DLQ队列,且不会⾃动清除;对于过期的消息进⼊死信队列还有⼀些可选的策略:放⼊各⾃的死信通道、保存在⼀个共享的队列(默认),且可以设置是否将过期消息放⼊队列的开关以及死信队列消息过期时间。
1)直接抛弃死信队列
AcitveMQ提供了⼀个便捷的插件:DiscardingDLQBrokerPlugin,来抛弃DeadLetter。
如果开发者不需要关⼼DeadLetter,可以使⽤此策略。
配置⽰例
1. <broker>
2. ...
3. <plugins>
4. <!-- 丢弃所有死信-->
5. <discardingDLQBrokerPlugindropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true" />
6. <!-- 丢弃指定死信-->
7. <!-- <discardingDLQBrokerPlugindropOnly="MY.EXAMPLE.TOPIC.29 MY.EXAMPLE.QUEUE.87" reportInterval="1000" />-->
8. <!--使⽤丢弃正则匹配到死信-->
9. <!--<discardingDLQBrokerPlugindropOnly="MY.EXAMPLE.TOPIC.[0-9]{3} MY.EXAMPLE.QUEUE.[0-9]{3}" reportInterval="3000"/>-->
10. </plugins>
11. ...
12. </broker>
2)定时抛弃死信队列
默认情况下,ActiveMQ永远不会过期发送到DLQ的消息。
但是,从ActiveMQ 5.12开始,deadLetterStrategy⽀持expiration属性,其值以毫秒为单位。
配置⽰例
1. <policyEntryqueue=">"…>
2. ...
3. <deadLetterStrategy>
4. <sharedDeadLetterStrategy processExpired="true" expiration="30000"/>
5. </deadLetterStrategy>
6. ...
7. </policyEntry>
3、慢消费者策略设置
Broker将会启动⼀个后台线程⽤来检测所有的慢速消费者,并定期关闭关闭它们;中断慢速消费者,慢速消费将会被关闭。
abortConnection是否关闭连接;如果慢速消费者最后⼀个ACK距离现在的时间间隔超过阀maxTimeSinceLastAck,则中断慢速消费者。
配置⽰例
1. <policyEntryqueue=">"…>
2. …
3. <slowConsumerStrategy>
4. <abortSlowConsumerStrategyabortConnection="false"/> <!--不关闭底层链接-->
5. </slowConsumerStrategy>
6. …
7. </policyEntry>
4、测试
1)配置activemq.xml;
2)批量消息发送;
3)等待若⼲秒,消息减少;
4)等待若⼲秒,消息队列清除(设置了抛弃死信队列);
5)等待若⼲秒,消息队列清除(未设置抛弃死信队列,设置了死信队列过期时间);
6)等待若⼲秒,消息队列清除(不抛弃死信队列,死信队列不过期);
5、参考⽹址
完整配置
1. <!--
2. Licensed to the Apache Software Foundation (ASF) under one or more
3. contributor license agreements. See the NOTICE file distributed with
4. this work for additional information regarding copyright ownership.
5. The ASF licenses this file to You under the Apache License, Version 2.0
6. (the "License"); you may not use this file except in compliance with
7. the License. You may obtain a copy of the License at
8.
9. /licenses/LICENSE-2.0
10.
11. Unless required by applicable law or agreed to in writing, software
12. distributed under the License is distributed on an "AS IS" BASIS,
13. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14. See the License for the specific language governing permissions and
15. limitations under the License.
16. -->
17. <!-- START SNIPPET: example -->
18. <beans
19. xmlns="/schema/beans"
20. xmlns:xsi="/2001/XMLSchema-instance"
21. xsi:schemaLocation="/schema/beans /schema/beans/spring-beans.xsd
22. /schema/core /schema/core/activemq-core.xsd">
23.
24. <!-- Allows us to use system properties as variables in this configuration file -->
25. <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
26. <property name="locations">
27. <value>file:${activemq.conf}/credentials.properties</value>
28. </property>
29. </bean>
30.
31. <!-- Allows accessing the server log -->
32. <bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
33. lazy-init="false" scope="singleton"
34. init-method="start" destroy-method="stop">
35. </bean>
36.
37. <!--
38. The <broker> element is used to configure the ActiveMQ broker.
39. -->
40. <broker xmlns="/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" schedulePeriodForDestinationPurge="10000">
41. <destinationPolicy>
42. <policyMap>
43. <policyEntries>
44. <policyEntry queue=">" gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000">
45. <deadLetterStrategy>
46. <sharedDeadLetterStrategy processExpired="true" expiration="30000"/>
47. </deadLetterStrategy>
48. </policyEntry>
49. <policyEntry topic=">" >
50. <!-- The constantPendingMessageLimitStrategy is used to prevent
51. slow topic consumers to block producers and affect other consumers
52. by limiting the number of messages that are retained
53. For more information, see:
54. /slow-consumer-handling.html
55. -->
56. <pendingMessageLimitStrategy>
57. <constantPendingMessageLimitStrategy limit="1000"/>
58. </pendingMessageLimitStrategy>
59. </policyEntry>
60. </policyEntries>
61. </policyMap>
62. </destinationPolicy>
63.
64. <!--
65. The managementContext is used to configure how ActiveMQ is exposed in
66. JMX. By default, ActiveMQ uses the MBean server that is started by
67. the JVM. For more information, see:
68. /jmx.html
69. -->
70. <managementContext>
71. <managementContext createConnector="false"/>
72. </managementContext>
73.
74. <!--
75. Configure message persistence for the broker. The default persistence
76. mechanism is the KahaDB store (identified by the kahaDB tag).
77. For more information, see:
78.
79. /persistence.html
80. -->
81. <persistenceAdapter>
82. <kahaDB directory="${activemq.data}/kahadb"/>
83. </persistenceAdapter>
84. <!--
85. The systemUsage controls the maximum amount of space the broker will
86. use before disabling caching and/or slowing down producers. For more information, see:
87. /producer-flow-control.html
88. -->
89. <systemUsage>
90. <systemUsage>
91. <memoryUsage>
92. <memoryUsage percentOfJvmHeap="70" />
93. </memoryUsage>
94. <storeUsage>
95. <storeUsage limit="100 gb"/>
96. </storeUsage>
97. <tempUsage>
98. <tempUsage limit="50 gb"/>
99. </tempUsage>
100. </systemUsage>
101. </systemUsage>
102.
103. <!--
104. The transport connectors expose ActiveMQ over a given protocol to
105. clients and other brokers. For more information, see:
106. /configuring-transports.html
107. -->
108. <transportConnectors>
109. <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
110. <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> 111. <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> 112. <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> 113. <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> 114. <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> 115. </transportConnectors>
116.
117. <!-- destroy the spring context on shutdown to stop jetty -->
118. <shutdownHooks>
119. <bean xmlns="/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
120. </shutdownHooks>
121.
122. <plugins>
123. <!-- 86,400,000ms = 1 day -->
124. <timeStampingBrokerPlugin ttlCeiling="30000" zeroExpirationOverride="30000" />
125. <!-- <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true" />-->
126. </plugins>
127. </broker>
128.
129. <!--
130. Enable web consoles, REST and Ajax APIs and demos
131. The web consoles requires by default login, you can disable this in the jetty.xml file
132. Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
133. -->
134. <import resource="jetty.xml"/>
135. </beans>
136. <!-- END SNIPPET: example -->。