How do you implement manual message acknowledgement with RabbitMQ in NestJS?

Q: How do you implement manual message acknowledgement with RabbitMQ in NestJS?

@Controller() export class OrdersController { @EventPattern('order_placed') async handleOrderPlaced( @Payload() data: OrderPlacedEvent, @Ctx() ctx: RmqContext, ): Promise { const channel = ctx.getChannelRef(); const originalMsg = ctx.getMessage(); try { await this.ordersService.processOrder(data); channel.ack(originalMsg); // success — remove from queue } catch (error) { // nack(msg, allUpTo, requeue) channel.nack(originalMsg, false, true); // failure — requeue for retry // channel.nack(originalMsg, false, false) — dead-letter instead } } } // Dead-letter queue — send failed messages after max retries options: { queueOptions: { durable: true, arguments: { 'x-dead-letter-exchange': 'dlx', 'x-dead-letter-routing-key': 'orders.dead', 'x-message-ttl': 60000, // retry after 60s via TTL DLQ }, }, } noAck: false must be set in the microservice options — otherwise NestJS auto-acks before your handler runs. channel.ack(msg) — removes the message from the queue after successful processing. channel.nack(msg, false, true) — returns the message to the queue for redelivery. channel.nack(msg, false, false) — dead-letters the message instead of requeuing. Always ack or nack in a try/finally to prevent message leaks if the handler throws unexpectedly.

Difficulty: 5/10

RabbitMQ, NestJS microservices, manual acknowledgement

Access the AMQP channel via RmqContext.getChannelRef() and the raw message via ctx.getMessage(). Call channel.ack() on success and channel.nack() on failure. The second and third arguments to nack() control whether the message is requeued or dead-lettered.

Manual ack/nack with dead-letter queue setup

Manual acknowledgement rules:

1
noAck: false must be set in the microservice options — otherwise NestJS auto-acks before your handler runs.
2

How do you implement manual message acknowledgement with RabbitMQ in NestJS?

Difficulty: 5/10

RabbitMQ, NestJS microservices, manual acknowledgement

Access the AMQP channel via RmqContext.getChannelRef() and the raw message via ctx.getMessage(). Call channel.ack() on success and channel.nack() on failure. The second and third arguments to nack() control whether the message is requeued or dead-lettered.

Manual ack/nack with dead-letter queue setup

Manual acknowledgement rules:

1
noAck: false must be set in the microservice options — otherwise NestJS auto-acks before your handler runs.
2

How do you implement manual message acknowledgement with RabbitMQ in NestJS?

Access the AMQP channel via RmqContext.getChannelRef() and the raw message via ctx.getMessage(). Call channel.ack() on success and channel.nack() on failure. The second and third arguments to nack() control whether the message is requeued or dead-lettered.

How do you implement manual message acknowledgement with RabbitMQ in NestJS?

Access the AMQP channel via RmqContext.getChannelRef() and the raw message via ctx.getMessage(). Call channel.ack() on success and channel.nack() on failure. The second and third arguments to nack() control whether the message is requeued or dead-lettered.

Scenario Questions

Follow-up Questions