Graceful Shutdown

When your process exits, you need to stop producers and consumers in the right order to avoid losing in-flight messages or leaving broker resources open. amqpx provides RabbitCloser for this.

RabbitCloser

RabbitCloser closes provided entities in a fixed sequence: producers → consumers → channels → connections. This order ensures all pending publishes are flushed before consumers stop, and all consumers have finished their handlers before the connection is torn down.

import { RabbitCloser } from 'amqpx'

const closer = new RabbitCloser(
  [connection],          // connections — closed last
  [orderConsumer],       // consumers
  [orderProducer],       // producers — closed first
)

RabbitCloser does not hook into any process signals (SIGTERM, SIGINT, etc.) — you are responsible for calling closer.close() at the right moment. A typical setup:

process.on('SIGTERM', async () => {
  await closer.close()
  process.exit(0)
})

Timeout

closer.close(timeout?) accepts an optional total budget in milliseconds for the entire shutdown sequence. The budget is shared across all stages — each stage receives whatever time remains after the previous stages have finished, so connections always get less time than producers:

await closer.close(30_000)  // 30 s total budget across producers, consumers, channels, connections

If a stage exhausts the remaining budget it throws — for example 'Producer close timed out', 'Consumer close timeout', 'Channel close timed out', or 'Connection close timed out'.

When timeout is omitted, the default value is 60 seconds.