Queue length limits in RabbitMQ - Step-by-Step Execution

Process Flow - Queue length limits

Start: Queue created

↓

Messages added to queue

↓

Check: Queue length < limit?

No→Reject or Drop message

Yes↓

Message stored in queue

↓

Consumer receives message

↓

Message removed from queue

↓

Repeat as messages arrive

This flow shows how RabbitMQ checks the queue length limit before accepting new messages. If the limit is reached, messages are rejected or dropped.

Execution Sample

RabbitMQ

rabbitmqctl set_policy TTL "^myqueue$" '{"max-length":3, "overflow":"reject-publish"}' --apply-to queues

# Publish 4 messages to 'myqueue'

# Observe queue length and message acceptance

This example sets a max length of 3 messages on 'myqueue' and then tries to add 4 messages, showing how the limit affects message acceptance.

Process Table

Step	Action	Queue Length Before	Message Added?	Queue Length After	Result
1	Add message 1	0	Yes	1	Message accepted
2	Add message 2	1	Yes	2	Message accepted
3	Add message 3	2	Yes	3	Message accepted
4	Add message 4	3	No	3	Message rejected due to max-length limit
5	Consumer receives message	3	N/A	2	Message removed from queue
6	Add message 4 retry	2	Yes	3	Message accepted after space freed

💡 Message 4 initially rejected because queue length reached max-length 3

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6
queue_length	0	1	2	3	3	2	3

Key Moments - 3 Insights

Why was the 4th message rejected at step 4?

Because the queue length was already at the max-length limit of 3, RabbitMQ rejected the new message to prevent overflow, as shown in execution_table row 4.

What happens when a consumer removes a message from the queue?

The queue length decreases by one, freeing space for new messages. This is shown at step 5 where queue_length drops from 3 to 2, allowing message 4 to be accepted later.

Can messages be added again after reaching the max-length limit?

Yes, once the queue length is below the limit (after consumers remove messages), new messages can be accepted again, as seen at step 6.

Visual Quiz - 3 Questions

Look at the execution table, what is the queue length after step 3?

A 3

B 2

C 1

D 0

💡 Hint

Check the 'Queue Length After' column at step 3 in the execution_table.

At which step is the message rejected due to the queue length limit?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for 'Message rejected' in the 'Result' column of the execution_table.

If the max-length was set to 5 instead of 3, what would happen at step 4?

A Message 4 would be rejected

B Queue length would decrease

C Message 4 would be accepted

D Consumer would remove a message

💡 Hint

Refer to the queue length checks in the execution_table and how max-length affects message acceptance.

Concept Snapshot

RabbitMQ queue length limits control how many messages a queue can hold.
Set max-length in queue policy to limit messages.
When limit reached, new messages are rejected or dropped.
Consumers removing messages free space for new ones.
Useful to prevent memory overload and control flow.

Full Transcript

This visual execution trace shows how RabbitMQ enforces queue length limits. When messages are added, RabbitMQ checks if the queue length is below the max-length limit. If yes, the message is accepted and stored. If no, the message is rejected or dropped. When consumers receive messages, the queue length decreases, allowing new messages to be accepted again. The example sets a max-length of 3 on 'myqueue' and tries to add 4 messages. The first three are accepted, the fourth is rejected because the queue is full. After a consumer removes one message, the fourth message is accepted on retry. This helps control queue size and system resources.