此内容没有您所选择的语言版本。

Chapter 20. Message Expiry


Messages can be set with an optional time to live (TimeToLive) when sending them.
HornetQ will not deliver a message to a consumer after its time to live has been exceeded. If the message has not been delivered before the time to live is reached, the server can discard it.
HornetQ addresses can be assigned an expiry address so when messages are expired, the addresses are removed from the queue and sent to the expiry address. Many different queues can be bound to an expiry address. These expired messages can later be consumed for further inspection.

20.1. Message Expiry

Using HornetQ Core API, you can set an expiration time directly on the message:
// message will expire in 5000ms from now
message.setExpiration(System.currentTimeMillis() + 5000);
Copy to Clipboard Toggle word wrap
JMS MessageProducer allows you to set a TimeToLive for the messages it sent:
// messages sent by this producer will be retained for 5s (5000ms) before expiration           
producer.setTimeToLive(5000);
Copy to Clipboard Toggle word wrap
Expired messages which are consumed from an expiry address have the following properties:
HQ_ORIG_ADDRESS
a String property containing the original address of the expired message
HQ_ACTUAL_EXPIRY
a Long property containing the actual expiration time of the expired message
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat