Timeout handling in RPC in RabbitMQ - Commands & Configuration

Introduction

Sometimes when one program asks another for information, the answer can take too long or never come. Timeout handling in RPC helps stop waiting after a set time so the first program can keep working without freezing.

When your app asks another service for data but that service might be slow or unresponsive.

When you want to avoid your app freezing if the other side never replies.

When you want to retry a request if the first try takes too long.

When you want to log or alert if a request takes longer than expected.

When you want to keep your system responsive even if some parts fail.

Commands

Create a durable queue named rpc_queue where RPC requests will be sent. Durable means it survives server restarts.

Terminal

rabbitmqadmin declare queue name=rpc_queue durable=true

Expected Output

{"queue":{"name":"rpc_queue","vhost":"/","durable":true,"auto_delete":false,"arguments":{}}}

→

name=rpc_queue - Sets the queue name to rpc_queue

→

durable=true - Makes the queue survive RabbitMQ restarts

Send an RPC request message to rpc_queue with a reply_to address and a correlation_id to match the response.

Terminal

rabbitmqadmin publish routing_key=rpc_queue payload='{"request":"data"}' properties='{"reply_to":"amq.rabbitmq.reply-to","correlation_id":"12345"}'

Expected Output

{"routed":true}

→

routing_key=rpc_queue - Sends the message to the rpc_queue

→

properties - Sets reply_to and correlation_id for response tracking

Check the reply-to queue for a response message from the RPC server.

Terminal

rabbitmqadmin get queue=amq.rabbitmq.reply-to count=1

Expected Output

{"messages":[{"payload":"{\"response\":\"data\"}","properties":{"correlation_id":"12345"}}]}

→

queue=amq.rabbitmq.reply-to - Reads messages from the direct reply-to queue

→

count=1 - Fetches only one message

Try to get a reply message but stop waiting after 5 seconds to avoid hanging if no response arrives.

Terminal

timeout 5 rabbitmqadmin get queue=amq.rabbitmq.reply-to count=1

Expected Output

Timeout after 5 seconds

→

timeout 5 - Limits the command to 5 seconds max

Key Concept

If you remember nothing else from this pattern, remember: always set a timeout when waiting for RPC replies to keep your app responsive.

Common Mistakes

Not setting a timeout when waiting for the RPC reply.

The app can freeze indefinitely if the server never responds.

Use a timeout command or client-side timeout logic to stop waiting after a set time.

Not using correlation_id to match replies to requests.

You might process the wrong response or get confused if multiple requests are active.

Always set and check correlation_id to match each reply to its request.

Not setting reply_to property in the request message.

The server won't know where to send the response, so you never get a reply.

Set reply_to to a valid queue or use RabbitMQ's direct reply-to feature.

Summary

Create a durable queue to receive RPC requests.

Send RPC requests with reply_to and correlation_id properties.

Check the reply queue for responses matching the correlation_id.

Use a timeout to avoid waiting forever for a reply.