Dev Services for AMQP
Dev Services for AMQP automatically starts an AMQP 1.0 broker in dev mode and when running tests. So, you don’t have to start a broker manually. The application is configured automatically.
Dev Services for AMQP is automatically enabled unless:
quarkus.amqp.devservices.enabledis set to
all the Reactive Messaging AMQP channels have the
Dev Services for AMQP relies on Docker to start the broker.
If your environment does not support Docker, you will need to start the broker manually, or connect to an already running broker.
You can configure the broker access using the
Most of the time you need to share the broker between applications. Dev Services for AMQP implements a service discovery mechanism for your multiple Quarkus applications running in dev mode to share a single broker.
Dev Services for AMQP starts the container with the
If you need multiple (shared) brokers, you can configure the
quarkus.amqp.devservices.service-name attribute and indicate the broker name.
It looks for a container with the same value, or starts a new one if none can be found.
The default service name is
Sharing is enabled by default in dev mode, but disabled in test mode.
You can disable the sharing with
By default, Dev Services for AMQP picks a random port and configures the application.
You can set the port by configuring the
Dev Services for AMQP uses activemq-artemis-broker images.
You can configure the image and version using the
The configured image must be compatible with the