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

1.5.11. Accessing AMQP Message Properties and Headers


The message-id, correlation-id, user-id, subject, reply-to and content-type fields in the properties section of a 1.0 message can all be set or retrieved via accessors of the same name on the Message instance. The same is true of the durable, priority and ttl fields in the header section.
An AMQP 1.0 message has a delivery-count field within the header section. There is no direct accessor for this field. However if the value is greater than 1, then the Message::getRedelivered() method returns true. If Message::setRedelivered() is called with a value of true, then the delivery count is set to 1, else it is set to 0.
The application-properties section of a received 1.0 message is available via the properties map of the Message class. The properties map is used to populate the application-properties section when sending a message.
There are other fields defined in the AMQP 1.0 message format that do not have direct accessors on the Message class.
The format for the keys is x-amqp-<field-name>. The keys in use are: x-amqp-first-acquirer and x-amqp-delivery-count for the header section, and x-amqp-to, x-amqp-absolute-expiry-time, x-amqp-creation-time, x-amqp-group-id, x-amqp-qroup-sequence and x-amqp-reply-to-group-id for the properties section.
In addition the delivery- and message- annotations sections are available via a nested map with key x-amqp-delivery-annotations and x-amqp-message-annotations respectively.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

Theme

© 2025 Red Hat