This guide walks you through the process of creating a Spring Boot application that publishes and subscribes to a RabbitMQ AMQP server.
You will build an application that publishes a message by using Spring AMQP’s RabbitTemplate and subscribes to the message on a POJO by using MessageListenerAdapter.
Before you can build your messaging application, you need to set up a server to handle receiving and sending messages. https://raw.githubusercontent.com/spring-guides/getting-started-macros/main/docker_compose_support.adoc
If you choose to run the RabbitMQ server yourself instead of using Spring Boot Docker Compose support, you have a few options:
-
Download the server and manually run it
-
Install with Homebrew, if you use a Mac
-
Manually run the
compose.yamlfile withdocker-compose up
If you go with any of these alternate approaches, you should remove the spring-boot-docker-compose dependency from the Maven or Gradle build file.
You will also need to add configuration to an application.properties file, as described in greater detail in the [_preparing_to_build_the_application] section.
As mentioned earlier, this guide assumes that you use Docker Compose support in Spring Boot, so additional changes to application.properties are not required at this point.
You can use this pre-initialized project and click Generate to download a ZIP file. This project is configured to fit the examples in this guide.
To manually initialize the project:
-
Navigate to start.spring.io. This service pulls in all the dependencies you need for an application and does most of the setup for you.
-
Choose either Gradle or Maven and the language you want to use. This guide assumes that you chose Java.
-
Click Dependencies and select Spring for RabbitMQ and Docker Compose Support.
-
Click Generate.
-
Download the resulting ZIP file, which is an archive of an application that is configured with your choices.
|
Note
|
If your IDE has the Spring Initializr integration, you can complete this process from your IDE. |
With any messaging-based application, you need to create a receiver that responds to
published messages. The following listing (from
src/main/java/com/example/messagingrabbitmq/Receiver.java) shows how to do so:
link:complete/src/main/java/com/example/messagingrabbitmq/Receiver.java[role=include]The Receiver is a POJO that defines a method for receiving messages. When you register
it to receive messages, you can name it anything you want.
|
Note
|
For convenience, this POJO also has a CountDownLatch. This lets it signal that the
message has been received. This is something you are not likely to implement in a
production application.
|
Spring AMQP’s RabbitTemplate provides everything you need to send and receive messages
with RabbitMQ. However, you need to:
-
Configure a message listener container.
-
Declare the queue, the exchange, and the binding between them.
-
Configure a component to send some messages to test the listener.
|
Note
|
Spring Boot automatically creates a connection factory and a RabbitTemplate, reducing the amount of code you have to write. |
You will use RabbitTemplate to send messages, and you will register a Receiver with
the message listener container to receive messages. The connection factory drives both,
letting them connect to the RabbitMQ server. The following listing (from
src/main/java/com/example/messagingrabbitmq/MessagingRabbitmqApplication.java) shows how
to create the application class:
link:complete/src/main/java/com/example/messagingrabbitmq/MessagingRabbitmqApplication.java[role=include]The @SpringBootApplication annotation offers a number of benefits, as described in the reference documentation.
The bean defined in the listenerAdapter() method is registered as a message listener in
the container (defined in container()). It listens for messages on the spring-boot
queue. Because the Receiver class is a POJO, it needs to be wrapped in the
MessageListenerAdapter, where you specify that it invokes receiveMessage.
|
Note
|
JMS queues and AMQP queues have different semantics. For example, JMS sends queued messages to only one consumer. While AMQP queues do the same thing, AMQP producers do not send messages directly to queues. Instead, a message is sent to an exchange, which can go to a single queue or fan out to multiple queues, emulating the concept of JMS topics. |
The message listener container and receiver beans are all you need to listen for messages. To send a message, you also need a Rabbit template.
The queue() method creates an AMQP queue. The exchange() method creates a topic
exchange. The binding() method binds these two together, defining the behavior that
occurs when RabbitTemplate publishes to an exchange.
|
Note
|
Spring AMQP requires that the Queue, the TopicExchange, and the Binding be
declared as top-level Spring beans in order to be set up properly.
|
In this case, we use a topic exchange, and the queue is bound with a routing key of
foo.bar.#, which means that any messages sent with a routing key that begins with
foo.bar. are routed to the queue.
In this sample, test messages are sent by a CommandLineRunner, which also waits for the
latch in the receiver and closes the application context. The following listing (from
src/main/java/com.example.messagingrabbitmq/Runner.java) shows how it works:
link:complete/src/main/java/com/example/messagingrabbitmq/Runner.java[role=include]Notice that the template routes the message to the exchange with a routing key of
foo.bar.baz, which matches the binding.
In tests, you can mock out the runner so that the receiver can be tested in isolation.
The main() method starts that process by creating a Spring application context. This
starts the message listener container, which starts listening for messages. There is a
Runner bean, which is then automatically run. It retrieves the RabbitTemplate from the
application context and sends a Hello from RabbitMQ! message on the spring-boot queue.
Finally, it closes the Spring application context, and the application ends.
You can run the main method through your IDE.
Note that, if you have cloned the project from the solution repository, your IDE may look in the wrong place for the compose.yaml file.
You can configure your IDE to look in the correct place or you could use the command line to run the application.
The ./gradlew bootRun and ./mvnw spring-boot:run commands will launch the application and automatically find the compose.yaml file.
To run the code without Spring Boot Docker Compose support, you need a version of RabbitMQ running locally to connect to.
To do this, you can use Docker Compose, but you must first make two changes to the compose.yaml file.
First, modify the ports entry in compose.yaml to be '5672:5672'.
Second, add a container_name.
The compose.yaml should now be:
services:
rabbitmq:
container_name: 'guide-rabbit'
image: 'rabbitmq:latest'
environment:
- 'RABBITMQ_DEFAULT_PASS=secret'
- 'RABBITMQ_DEFAULT_USER=myuser'
ports:
- '5672:5672'
You can now run docker-compose up to start the RabbitMQ service.
Now you should have an external RabbitMQ server that is ready to accept requests.
Additionally, you need to tell Spring how to connect to the RabbitMQ server (this was handled automatically with Spring Boot Docker Compose support).
Add the following code to a new application.properties file in src/main/resources:
spring.rabbitmq.password=secret spring.rabbitmq.username=myuser
Regardless of how you chose to build and run the application, you should see the following output:
Sending message...
Received <Hello from RabbitMQ!>Congratulations! You have just developed a simple publish-and-subscribe application with Spring and RabbitMQ. You can do more with Spring and RabbitMQ than what is covered here, but this guide should provide a good start.
Additional Spring AMQP Samples
The following guides may also be helpful:
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent