Skip to content

Documentation updates for the new x-death updates logic #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 26, 2015
Merged

Documentation updates for the new x-death updates logic #1

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8af9093
Document changes in rabbitmq-server#78.
michaelklishin Mar 20, 2015
7e3c088
Document x-death event counter
michaelklishin Mar 24, 2015
a2c74ca
counter => count
michaelklishin Mar 25, 2015
14c036d
dlx.xml: Fix continuation in the x-death header fields list
dumbbell Mar 26, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions site/dlx.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,9 @@ args.put("x-dead-letter-routing-key", "some-routing-key");</pre>
<p>
The dead-lettering process adds an array to the header of
each dead-lettered message named <code>x-death</code>.
This array contains an entry for each time the message was
dead-lettered. Each such entry is a table that consists
This array contains an entry for each dead lettering event,
identified by a pair of <code>{queue, reason}</code>.
Each such entry is a table that consists
of several fields:
<ul>
<li><code>queue</code> - the name of the queue the
Expand All @@ -196,11 +197,13 @@ args.put("x-dead-letter-routing-key", "some-routing-key");</pre>
<li><code>exchange</code> - the exchange the message was
published to (note that this will be a dead letter
exchange if the message is dead lettered multiple
times), and</li>
times),</li>
<li><code>routing-keys</code> - the routing keys
(including <code>CC</code> keys but excluding
<code>BCC</code> ones) the message was published
with.</li>
with,</li>
<li><code>count</code> - how many times this message was
dead-lettered in this queue for this reason, and</li>
<li><code>original-expiration</code> (if the message was
dead-letterered due to <a
href="ttl.html#per-message-ttl">per-message TTL</a>) - the
Expand All @@ -209,6 +212,10 @@ args.put("x-dead-letter-routing-key", "some-routing-key");</pre>
message on dead-lettering in order to prevent it from
expiring again in any queues it is routed to.</li>
</ul>

In case <code>x-death</code> already contains an entry with
the same queue and dead lettering reason, its count field will be
incremented.
</p>
<p>
The <code>reason</code> is a name describing why the
Expand Down