Message acknowledgment in RabbitMQ - Mini Project: Build & Apply

Message acknowledgment

📖 Scenario: You are building a simple message consumer using RabbitMQ. Messages sent to a queue need to be acknowledged after processing to ensure they are not lost or re-delivered unnecessarily.

🎯 Goal: Learn how to set up a RabbitMQ consumer that receives messages from a queue and sends an acknowledgment back to the server after processing each message.

📋 What You'll Learn

Create a connection to RabbitMQ server

Declare a queue named task_queue

Consume messages from task_queue with manual acknowledgment

Send an acknowledgment after processing each message

💡 Why This Matters

🌍 Real World

Message acknowledgment ensures reliable processing in systems like order processing, notifications, and task queues where losing messages can cause errors or data loss.

💼 Career

Understanding message acknowledgment is essential for roles involving message brokers, distributed systems, and reliable data pipelines in DevOps and backend development.

1

Create connection and declare queue

Write code to create a connection to RabbitMQ server using pika.BlockingConnection with default parameters. Then create a channel and declare a queue named task_queue using channel.queue_declare(queue='task_queue', durable=True).

RabbitMQ

# Your code here

Hint

Use pika.BlockingConnection to connect and channel.queue_declare to declare the queue.

2

Set up consumer with manual acknowledgment

Add code to define a callback function named callback that takes ch, method, properties, body as parameters. Then use channel.basic_consume to consume messages from task_queue with auto_ack=False and the callback function.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()
channel.queue_declare(queue='task_queue', durable=True)

# Your code here

Hint

Define a callback function with the correct parameters and use basic_consume with auto_ack=False.

3

Send acknowledgment after processing

Inside the callback function, add code to send an acknowledgment for the received message using ch.basic_ack(delivery_tag=method.delivery_tag) after printing the message body.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()
channel.queue_declare(queue='task_queue', durable=True)

def callback(ch, method, properties, body):
    print(f"Received {body.decode()}")
    # Your code here

channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)

Hint

Use ch.basic_ack(delivery_tag=method.delivery_tag) to acknowledge the message.

4

Start consuming messages and print output

Add code to start consuming messages using channel.start_consuming(). This will keep the program running and processing messages. The program should print received messages as they arrive.

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()
channel.queue_declare(queue='task_queue', durable=True)

def callback(ch, method, properties, body):
    print(f"Received {body.decode()}")
    ch.basic_ack(delivery_tag=method.delivery_tag)

channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)

# Your code here

Hint

Use channel.start_consuming() to begin processing messages and print a waiting message before that.

Practice

1. What is the main purpose of message acknowledgment in RabbitMQ?

easy

A. To confirm that a message was received and processed successfully

B. To delete the message queue permanently

C. To create a new message exchange

D. To encrypt messages before sending

Solution

1. Step 1: Understand message acknowledgment role

   Message acknowledgment tells RabbitMQ that the consumer has processed the message successfully.

2. Step 2: Identify the purpose from options

   Only To confirm that a message was received and processed successfully describes confirming message processing, which prevents message loss.

3. Final Answer:

   To confirm that a message was received and processed successfully -> Option A

4. Quick Check:

   Message acknowledgment = Confirm processing [OK]

Hint: Acknowledgment means confirming message processed [OK]

Common Mistakes:

• Confusing acknowledgment with queue deletion
• Thinking acknowledgment creates exchanges
• Assuming acknowledgment encrypts messages

2. Which RabbitMQ client method is used to acknowledge a message after processing?

easy

A. basic_reject

B. basic_publish

C. basic_consume

D. basic_ack

Solution

1. Step 1: Recall RabbitMQ acknowledgment method

   The method to acknowledge a message is basic_ack, which confirms message processing.

2. Step 2: Match method to options

   Only basic_ack matches the acknowledgment method; others are for publishing, consuming, or rejecting.

3. Final Answer:

   basic_ack -> Option D

4. Quick Check:

   basic_ack = acknowledge message [OK]

Hint: Use basic_ack to confirm message processed [OK]

Common Mistakes:

• Using basic_publish to acknowledge
• Confusing basic_consume with acknowledgment
• Mistaking basic_reject as acknowledgment

3. Given this Python snippet using pika:

channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)

def callback(ch, method, properties, body):
    print(f"Received {body}")
    ch.basic_ack(delivery_tag=method.delivery_tag)

What will happen if basic_ack is not called inside callback?

medium

A. Messages will be lost after delivery

B. Messages will be automatically acknowledged

C. Messages will be requeued and redelivered

D. The queue will be deleted

Solution

1. Step 1: Understand auto_ack=False effect

   With auto_ack=False, messages must be manually acknowledged or they stay unacknowledged.

2. Step 2: Consequence of missing basic_ack

   If basic_ack is not called, RabbitMQ will requeue the message and redeliver it to consumers.

3. Final Answer:

   Messages will be requeued and redelivered -> Option C

4. Quick Check:

   No ack + auto_ack=False = redelivery [OK]

Hint: No ack with auto_ack false causes redelivery [OK]

Common Mistakes:

• Assuming messages are lost without ack
• Thinking messages auto-acknowledge without basic_ack
• Believing queue deletes on missing ack

4. You wrote this callback in Python with pika:

def callback(ch, method, properties, body):
    print(f"Processing {body}")
    ch.basic_ack(delivery_tag=method.delivery_tag + 1)

What is the problem with this acknowledgment call?

medium

A. The delivery tag is incorrect, causing ack failure

B. basic_ack does not accept delivery_tag parameter

C. The callback function is missing required parameters

D. basic_ack should be called before processing the message

Solution

1. Step 1: Check delivery_tag usage

   The delivery tag must match the exact tag from method.delivery_tag to acknowledge the correct message.

2. Step 2: Identify error in delivery_tag calculation

   Adding 1 to the delivery tag sends an invalid tag, so RabbitMQ will not acknowledge the message properly.

3. Final Answer:

   The delivery tag is incorrect, causing ack failure -> Option A

4. Quick Check:

   delivery_tag must match exactly [OK]

Hint: Use exact delivery_tag value for ack [OK]

Common Mistakes:

• Modifying delivery_tag before ack
• Thinking basic_ack lacks delivery_tag parameter
• Calling ack before processing message

5. You want to ensure that if your consumer crashes before acknowledging, the message is redelivered. Which combination of settings and code achieves this safely?

hard

A. Set auto_ack=True and call basic_ack in callback

B. Set auto_ack=False and call basic_ack with correct delivery_tag after processing

C. Set auto_ack=False and never call basic_ack

D. Set auto_ack=True and never call basic_ack

Solution

1. Step 1: Understand auto_ack impact on message safety

   Setting auto_ack=True acknowledges messages immediately, risking message loss if consumer crashes.

2. Step 2: Use manual acknowledgment for safe processing

   Setting auto_ack=False and calling basic_ack after processing ensures messages are only removed after success.

3. Step 3: Confirm correct delivery_tag usage

   Calling basic_ack with the exact delivery tag confirms the message was processed and prevents redelivery.

4. Final Answer:

   Set auto_ack=False and call basic_ack with correct delivery_tag after processing -> Option B

5. Quick Check:

   Manual ack + correct tag = safe redelivery [OK]

Hint: Use manual ack with correct tag for safe redelivery [OK]

Common Mistakes:

• Using auto_ack=True for critical messages
• Not calling basic_ack at all
• Calling basic_ack with wrong delivery_tag