Setting Up Spring AMQP: RabbitTemplate and @RabbitListener

Setting up Spring AMQP has three layers: connection, topology, and message flow — and skipping the topology layer is the most common mistake that causes messages to vanish silently.

Connection and auto-configuration:

• Add spring-boot-starter-amqp and configure broker host, port, and credentials in application.yml; Spring Boot auto-configures a CachingConnectionFactory and a RabbitAdmin from those properties
• RabbitAdmin creates topology declarations on the broker idempotently at startup, so redeclaring exchanges, queues, and bindings across restarts is safe

Topology declaration — the step people skip:

• Declare the exchange, queue, and binding as Spring beans in a @Configuration class; without this, messages vanish silently because no binding connects the exchange to a queue
• Missing declarations produce no startup error — the first publish drops into the void and the first listener throws a 404 NOT_FOUND channel error that's easy to misread

Message converter — the silent failure source:

• Always override the default message converter with Jackson2JsonMessageConverter; the default uses Java serialization, which is a security risk and doesn't interoperate with non-Java consumers
• The Jackson converter must be wired into both the RabbitTemplate and the listener container factory — mismatched converters between producer and consumer are the number-one cause of ListenerExecutionFailedException

Publishing and consuming:

• Inject RabbitTemplate and call convertAndSend for publishing; annotate methods with @RabbitListener for consuming; the critical tuning parameter is prefetch — default 250 means one slow consumer hoards messages

I recommend wiring a dead-letter exchange from day one and creating per-listener container factories when handlers have different concurrency needs, rather than retrofitting these after problems surface in production.