blocks|key|153341|text|JMS为您提供了一种设置消息过期的机制。请看下面的两个参考|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153342|setJMSExpiration(长期过期)：每条消息|ordered-list-item|offset|length|153343|ActiveMQ:如何设置消息过期：每条命令/每条消息|153344|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/javaee/1.3/api/javax/jms/Message.html#setJMSExpiration%2528long%2529|1|https://activemq.apache.org/how-do-i-set-the-message-expiration.html^0|0|0|M|0|0|0|H|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|H|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]|Q|$5|L|M|N|A|$O|R]]]]

JMS provides a mechanism for you to set expiry on messages. Look at the below two references

<ol>
<li><a href="https://docs.oracle.com/javaee/1.3/api/javax/jms/Message.html#setJMSExpiration%28long%29" rel="nofollow noreferrer">setJMSExpiration(long expiration)</a>: per message</li>
<li><a href="https://activemq.apache.org/how-do-i-set-the-message-expiration.html" rel="nofollow noreferrer">ActiveMQ: How do I set the message expiration</a>: per destionation/per message</li>
</ol>

blocks|key|308644|text|还请注意，客户-代理之间的时钟需要保持同步，以使到期正常工作。如果时钟不同步，那么当在代理上接收到消息时，来自客户端的过期集可能已经过期。或者客户时间在代理之前，所以到期时间比10秒长。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308645|我有点不明白为什么到期日是以客户时间为基础的。因此，AMQ提供了一个插件，通过重新调整时间来解决这个问题，只以经纪人为基础。请参阅https://activemq.apache.org/timestampplugin.html|offset|length|308646|entityMap|0|LINK|mutability|MUTABLE|url|https://activemq.apache.org/timestampplugin.html^0|0|1T|1C|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Also mind that clocks between client - broker need to be in sync, for the expiry to work properly. If the clocks is not in sync, then the expiry set from the client, may already be expired when the message is received on the broker. Or the client time is ahead of the broker, so the expiry is longer than the 10 secs.

It kinda beats me why the expiry is client time based. So AMQ offers a plugin, to fix this by realigning the time, to be broker based only. See <a href="https://activemq.apache.org/timestampplugin.html" rel="nofollow noreferrer">https://activemq.apache.org/timestampplugin.html</a>

blocks|key|309163|text|好的，setJMSExpiration(长期过期)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|309164|是当你是客户的时候你不能叫的东西。请看我在ActiveMQ论坛上的演讲。|309165|https://apache-qpid-developers.2158895.n2.nabble.com/MRG-Java-JMS-Expiration-td7171854.html|offset|length|309166|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2J|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

Well the 
 setJMSExpiration(long expiration): 

is something you MUST not call when you are the client. See my talk on this a bit on the ActiveMQ forum.

<a href="https://apache-qpid-developers.2158895.n2.nabble.com/MRG-Java-JMS-Expiration-td7171854.html" rel="nofollow noreferrer">https://apache-qpid-developers.2158895.n2.nabble.com/MRG-Java-JMS-Expiration-td7171854.html</a>

blocks|key|634257|text|在我们这边，我们选择通过使用部署在ActiveMQ服务本身中的camel路由将过期时间添加到特定的目的地。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|634258|唯一要做的就是创建一个XML文件，如下所示，名为setJMSExpiration.xml|offset|length|style|CODE|634259|<beans+xmlns="http://www.springframework.org/schema/beans"++
+++xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+++xsi:schemaLocation="
+++++http://camel.apache.org/schema/spring+http://camel.apache.org/schema/spring/camel-spring.xsd
+++++http://www.springframework.org/schema/beans+http://www.springframework.org/schema/beans/spring-beans.xsd">

++<camelContext+id="camel-set-expiration"+xmlns="http://camel.apache.org/schema/spring">
++++
++++<route+id="setJMSExpiration.my.queue.dlq">
++++++<from+uri="broker:queue:MY.QUEUE.DLQ"/>
++++++++<setHeader+headerName="JMSExpiration">
++++++++++
++++++++++<spel>#{T(java.lang.System).currentTimeMillis()+%2B+86400000}</spel>
++++++++</setHeader>
++++++<to+uri="broker:queue:MY.QUEUE.DLQ"/>
++++</route>
++++<route+id="setJMSExpiration.another.queue">
++++++<from+uri="broker:queue:ANOTHER.QUEUE"/>
++++++++<setHeader+headerName="JMSExpiration">
++++++++++
++++++++++<spel>#{T(java.lang.System).currentTimeMillis()+%2B+432000000}</spel>
++++++++</setHeader>
++++++<to+uri="broker:queue:ANOTHER.QUEUE"/>
++++</route>
++</camelContext>
</beans>|code-block|syntax|javascript|634260|并将其导入您的activemq.xml配置中：|634261|
<import+resource="setJMSExpiration.xml"/>|634262|或者，如果不希望过期的消息到达ActiveMQ.DLQ队列，也可以提供特定的ActiveMQ.DLQ。|634263|<policyEntry+queue="MY.QUEUE.DLQ">
++++<deadLetterStrategy>
++++++++<sharedDeadLetterStrategy+processExpired="false"+/>
++++</deadLetterStrategy>
</policyEntry>
<policyEntry+queue="ANOTHER.QUEUE">
++++<deadLetterStrategy>
++++++++<sharedDeadLetterStrategy+processExpired="false"+/>
++++</deadLetterStrategy>
</policyEntry>|634264|这种方式的唯一限制是，您不能轻易地使用通配符，因为它是在这里编码的(您可以，但它将需要通过使用JMS目标头在camel路由)。|634265|我们试图让生产者定义timeToLive+(并尽可能强制他们)，但并不总是能够强迫他们更改代码，这是为了最小化这些路由的数量。|634266|entityMap^0|0|O|K|0|0|7|C|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

On our side we choose to add expiration time to specific destinations by using a camel route deployed in the ActiveMQ service itself.

The only thing to do is creating a XML file like the following with name e.g. <code>setJMSExpiration.xml</code>:

<pre><code>&lt;beans xmlns="http://www.springframework.org/schema/beans" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="
 http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd
 http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"&gt;

 &lt;camelContext id="camel-set-expiration" xmlns="http://camel.apache.org/schema/spring"&gt;
 &lt;!-- Copy route for each destination to expire --&gt;
 &lt;route id="setJMSExpiration.my.queue.dlq"&gt;
 &lt;from uri="broker:queue:MY.QUEUE.DLQ"/&gt;
 &lt;setHeader headerName="JMSExpiration"&gt;
 &lt;!-- Message will expire after 1 day --&gt;
 &lt;spel&gt;#{T(java.lang.System).currentTimeMillis() + 86400000}&lt;/spel&gt;
 &lt;/setHeader&gt;
 &lt;to uri="broker:queue:MY.QUEUE.DLQ"/&gt;
 &lt;/route&gt;
 &lt;route id="setJMSExpiration.another.queue"&gt;
 &lt;from uri="broker:queue:ANOTHER.QUEUE"/&gt;
 &lt;setHeader headerName="JMSExpiration"&gt;
 &lt;!-- Message will expire after 5 days --&gt;
 &lt;spel&gt;#{T(java.lang.System).currentTimeMillis() + 432000000}&lt;/spel&gt;
 &lt;/setHeader&gt;
 &lt;to uri="broker:queue:ANOTHER.QUEUE"/&gt;
 &lt;/route&gt;
 &lt;/camelContext&gt;
&lt;/beans&gt;
</code></pre>

and import it in your <code>activemq.xml</code> config with:

<pre><code>&lt;!-- Add default Expiration (file in the same directory) --&gt;
&lt;import resource="setJMSExpiration.xml"/&gt;
</code></pre>

Alternatively you can also provide specific <a href="https://activemq.apache.org/per-destination-policies.html" rel="nofollow noreferrer">per destination policies</a> if you don't want the expired messages to reach the ActiveMQ.DLQ queue.

<pre><code>&lt;policyEntry queue="MY.QUEUE.DLQ"&gt;
 &lt;deadLetterStrategy&gt;
 &lt;sharedDeadLetterStrategy processExpired="false" /&gt;
 &lt;/deadLetterStrategy&gt;
&lt;/policyEntry&gt;
&lt;policyEntry queue="ANOTHER.QUEUE"&gt;
 &lt;deadLetterStrategy&gt;
 &lt;sharedDeadLetterStrategy processExpired="false" /&gt;
 &lt;/deadLetterStrategy&gt;
&lt;/policyEntry&gt;
</code></pre>

The only limitation of this way is that you cannot easily use wildcards as it is coded here (you can, but it'll need some adaptations by using JMS destination header in the camel route).

We try to let the producers to define the timeToLive (and force them as much as possible) but it is not always possible to force them to change their code, this to minimize the number of such routes.

blocks|key|308657|text|端点选项timeToLive+(http://camel.apache.org/jms.html)为我解决了所描述的问题，消息在300000毫秒后从队列中删除。例如"activemq:Q.QUEUE?disableReplyTo=true&timeToLive=300000“|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|308658|设置标头JMSExpiration，在我的情况下不会导致从队列中自动删除消息。但是timetolive.html医生给了我一个提示。|308659|entityMap|0|LINK|mutability|MUTABLE|url|http://camel.apache.org/jms.html|1|https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rwsf_prjms_timetolive.html^0|4|A|3C|A|G|W|0|0|15|F|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|H|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

Endpoint option timeToLive (<a href="http://camel.apache.org/jms.html" rel="nofollow noreferrer">http://camel.apache.org/jms.html</a>) worked for me as a solution for the described problem, messages are removed from a queue after 300000 miliseconds.
e.g. "activemq:Q.QUEUE?disableReplyTo=true&amp;timeToLive=300000"

Setting header JMSExpiration, didn't cause removing message from a queue automatically in my case. 
But this doc <a href="https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rwsf_prjms_timetolive.html" rel="nofollow noreferrer">https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rwsf_prjms_timetolive.html</a> gave me a hint.

I have a system implementing Camel and ActiveMQ for communication between some servers. I would like to know if there is a way to automatically expire and clear-out messages sent to a queue after X period of time. Since the originating server (filling the queue) wont know if anyone is picking up the messages, I don't want my queue to grow until its so large that something crashes. Bonus karma points to someone who can help and provide the java dsl way to implement this feature.

Solution
 

<pre><code>// expire message after 2 minutes
long ttl = System.currentTimeMillis() + 120000;
// send our info one-way to the group topic
camelTemplate.sendBodyAndHeader("jms:queue:stats", ExchangePattern.InOnly, stats, "JMSExpiration", ttl);
</code></pre>

Auto expiration of messages in Camel

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个实现Camel和ActiveMQ的系统，用于某些服务器之间的通信。我想知道是否有一种方式，自动过期和清除发送到队列的消息后，X段时间。由于原始服务器(填充队列)将不知道是否有人正在接收消息，所以我不希望队列增长，直到它太大以至于某些东西崩溃。奖励业力指向能够帮助和提供java实现此功能的方法的人。溶液// expire message after 2 minuteslong ttl = S

问骆驼中消息的自动过期
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问骆驼中消息的自动过期EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问骆驼中消息的自动过期
EN