Publisher confirms in RabbitMQ - Commands & Configuration

Introduction

When sending messages to RabbitMQ, you want to be sure the messages are safely received by the server. Publisher confirms let your app know when messages are successfully stored, so you can avoid losing data.

When you want to make sure your messages are not lost if RabbitMQ crashes.

When your app sends important data that must be confirmed as received before continuing.

When you want to retry sending messages only if the server did not confirm them.

When you want to monitor message delivery success in real time.

When you want to avoid blocking your app while waiting for server acknowledgments.

Commands

Check that RabbitMQ server is running and ready to accept connections.

Terminal

rabbitmqctl status

Expected Output

Status of node rabbit@localhost ...

[{pid,12345},

 {running_applications,[

  {rabbit,"RabbitMQ","3.11.10"},

  {os_mon,"CPO  CXC 138 46","2.4"}

 ]},

 {os,{unix,linux}},

 {memory,[{total,12345678}]},

 {alarms,[]}]

Run a Python script that connects to RabbitMQ, enables publisher confirms, sends a message, and waits for confirmation.

Terminal

python3 publisher_confirms.py

Expected Output

Message published with confirmation

Key Concept

If you remember nothing else from this pattern, remember: publisher confirms let your app know when RabbitMQ safely received your messages.

Code Example

RabbitMQ

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

channel.confirm_delivery()

message = 'Hello, RabbitMQ with confirms!'

if channel.basic_publish(exchange='', routing_key='test_queue', body=message):
    print('Message published with confirmation')
else:
    print('Message could not be confirmed')

connection.close()

Common Mistakes

Not enabling publisher confirms on the channel before publishing messages.

Without enabling confirms, the server does not send acknowledgments, so your app cannot know if messages were received.

Call the method to enable publisher confirms on the channel before sending messages.

Ignoring the confirmation callback or not waiting for confirms after publishing.

If you don't wait or listen for confirms, you lose the benefit of knowing message delivery status.

Implement a callback or wait synchronously for confirms after publishing.

Summary

Check RabbitMQ server status to ensure it is running.

Enable publisher confirms on the channel before sending messages.

Publish messages and wait for confirmation to ensure delivery.

Practice

1. What does enabling publisher confirms in RabbitMQ do?

easy

A. It automatically retries sending messages on failure.

B. It encrypts messages before sending.

C. It tells you if RabbitMQ accepted your message.

D. It queues messages without sending them.

Solution

1. Step 1: Understand the purpose of publisher confirms

   Publisher confirms notify the sender if the message was accepted by RabbitMQ.

2. Step 2: Compare with other options

   Retrying, encrypting, or queuing without sending are unrelated to confirms.

3. Final Answer:

   It tells you if RabbitMQ accepted your message. -> Option C

4. Quick Check:

   Publisher confirms = message acceptance notification [OK]

Hint: Publisher confirms confirm message acceptance by RabbitMQ [OK]

Common Mistakes:

• Confusing confirms with message encryption
• Thinking confirms retry messages automatically
• Assuming confirms delay message sending

2. Which method must be called on a RabbitMQ channel to enable publisher confirms?

easy

A. enableConfirms()

B. setConfirmMode()

C. startConfirm()

D. confirmSelect()

Solution

1. Step 1: Recall the correct method name

   The method to enable confirms on a channel is confirmSelect().

2. Step 2: Verify other options

   Other method names like enableConfirms() or startConfirm() do not exist in RabbitMQ API.

3. Final Answer:

   confirmSelect() -> Option D

4. Quick Check:

   Enable confirms = confirmSelect() [OK]

Hint: Enable confirms by calling confirmSelect() on the channel [OK]

Common Mistakes:

• Using incorrect method names like enableConfirms()
• Forgetting to call confirmSelect() before publishing
• Confusing confirmSelect() with waitForConfirms()

3. Given this code snippet, what will waitForConfirms() return if the message was accepted?

channel.confirmSelect();
channel.basicPublish(exchange, routingKey, props, body);
boolean confirmed = channel.waitForConfirms();
System.out.println(confirmed);

medium

A. false

B. true

C. null

D. Exception thrown

Solution

1. Step 1: Understand waitForConfirms() behavior

   This method returns true if RabbitMQ accepted the message, false otherwise.

2. Step 2: Given the message was accepted

   The variable confirmed will be true, so printing it outputs 'true'.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Message accepted = waitForConfirms() returns true [OK]

Hint: waitForConfirms() returns true if message accepted [OK]

Common Mistakes:

• Expecting waitForConfirms() to return false on success
• Assuming it returns null or throws exception on success
• Confusing waitForConfirms() with asynchronous callbacks

4. What is wrong with this code snippet for enabling publisher confirms?

channel.basicPublish(exchange, routingKey, props, body);
channel.confirmSelect();
boolean confirmed = channel.waitForConfirms();

medium

A. confirmSelect() must be called before basicPublish()

B. waitForConfirms() cannot be called after publishing

C. basicPublish() requires a callback parameter

D. confirmSelect() should be called after waitForConfirms()

Solution

1. Step 1: Check order of method calls

   confirmSelect() must be called before publishing to enable confirms.

2. Step 2: Identify the error

   In the snippet, confirmSelect() is called after basicPublish(), so confirms are not enabled when publishing.

3. Final Answer:

   confirmSelect() must be called before basicPublish() -> Option A

4. Quick Check:

   Enable confirms before publishing [OK]

Hint: Call confirmSelect() before publishing messages [OK]

Common Mistakes:

• Calling confirmSelect() after publishing
• Thinking waitForConfirms() disables confirms
• Believing basicPublish() needs a callback for confirms

5. You want to ensure your application only proceeds after RabbitMQ confirms message acceptance. Which sequence of calls correctly implements this using publisher confirms?

hard

A. channel.confirmSelect(); channel.basicPublish(...); channel.waitForConfirms();

B. channel.basicPublish(...); channel.waitForConfirms(); channel.confirmSelect();

C. channel.waitForConfirms(); channel.confirmSelect(); channel.basicPublish(...);

D. channel.basicPublish(...); channel.confirmSelect(); channel.waitForConfirms();

Solution

1. Step 1: Enable confirms before publishing

   Call confirmSelect() first to enable confirms on the channel.

2. Step 2: Publish the message and wait for confirmation

   After basicPublish(...), call waitForConfirms() to block until RabbitMQ confirms acceptance.

3. Final Answer:

   channel.confirmSelect(); channel.basicPublish(...); channel.waitForConfirms(); -> Option A

4. Quick Check:

   Enable confirms, publish, then wait [OK]

Hint: Enable confirms, publish, then waitForConfirms() [OK]

Common Mistakes:

• Calling confirmSelect() after publishing
• Waiting for confirms before publishing
• Not calling waitForConfirms() at all