Apache/activemq-artemis
1
0
Fork 0
mirror of https://github.com/apache/activemq-artemis.git synced 2025-02-06 10:09:01 +00:00
Code Issues Packages Projects Releases Wiki Activity
activemq-artemis/docs/user-manual/en/copied-message-properties.md
Justin Bertram 7096bc187a ARTEMIS-2649 always over-write ORIG message props 
ORIG message propertes like _AMQ_ORIG_ADDRESS are added to messages
during various broker operations (e.g. diverting a message, expiring a
message, etc.). However, if multiple operations try to set these
properties on the same message (e.g. administratively moving a message
which eventually gets sent to a dead-letter address) then important
details can be lost. This is particularly problematic when using
auto-created dead-letter or expiry resources which use filters based on
_AMQ_ORIG_ADDRESS and can lead to message loss.

This commit simply over-writes the existing ORIG properties rather than
preserving them so that the most recent information is available.
2020-06-01 15:19:34 -04:00

1.4 KiB
Raw Blame History

Properties for Copied Messages

There are several operations within the broker that result in copying a message. These include:

  • Diverting a message from one address to another.
  • Moving an expired message from a queue to the configured expiry-address
  • Moving a message which has exceeded its max-delivery-attempts from a queue to the configured dead-letter-address
  • Using the management API to administratively move messages from one queue to another

When this happens the body and properties of the original message are copied to a new message. However, the copying process removes some potentially important pieces of data so those are preserved in the following special message properties:

  • _AMQ_ORIG_ADDRESS

    a String property containing the original address of the message

  • _AMQ_ORIG_QUEUE

    a String property containing the original queue of the message

  • _AMQ_ORIG_MESSAGE_ID

    a String property containing the original message ID of the message

It's possible for the aforementioned operations to be combined. For example, a message may be diverted from one address to another where it lands in a queue and a consumer tries & fails to consume it such that the message is then sent to a dead-letter address. Or a message may be administratively moved from one queue to another where it then expires.

In cases like these the ORIG properties will contain the information from the last (i.e. most recent) operation.