The listener container now supports dynamic scaling of the number of consumers based on workload, or the concurrency can be programmatically changed without stopping the container. See Section 3.12, “Listener Concurrency”.
The listener container now permits the queue(s) on which it is listening to be modified at runtime. Also, the container will now start if at least one of its configured queues is available for use. See Section 3.14, “Listener Container Queues”
This listener container will now redeclare any auto-delete queues during startup. See the section called “'auto-delete' Queues”.
The listener container now supports consumer arguments, allowing the
x-priority argument to be set. See Section 3.5.2, “Asynchronous Consumer”.
SimpleMessageListenerContainer can now be configured
with a single
exclusive consumer, preventing other consumers from
listening to the queue. See Section 3.13, “Exclusive Consumer”.
It is now possible to have the Broker generate the queue name, regardless of durable, autoDelete and exclusive settings. See Section 3.8, “Configuring the broker”.
Previously, omitting the
key attribute from a
direct-exchange configuration caused the queue or exchange to be bound with an
empty string as the routing key. Now it is bound with the
the name of the provided
Users wishing to bind with an empty string routing key need to specify
provides several synchronous
receiveAndReply methods. These are implemented
For more information see Section 3.5, “Receiving messages”.
RabbitTemplate now supports configuring a
RetryTemplate to attempt retries (with optional back off
policy) for when the broker is not available. For more information see
Section 3.3.1, “Adding Retry Capabilities”.
The caching connection factory can now be configured to cache
Channels instead of using a single
connection and caching just
Channels. See Section 3.2, “Connection and Resource Management”.
<binding> now supports parsing of
<binding-arguments> sub-element. The
<binding> now can be configured with a
key/value attribute pair
(to match on a single header)
or with a
<binding-arguments> sub-element, allowing matching on multiple
headers; these options are mutually exclusive. See Section 3.8, “Configuring the broker”.
SimpleRoutingConnectionFactory has been introduced,
to allow configuration of
ConnectionFactories mapping to determine
ConnectionFactory to use at runtime.
See Section 3.2.2, “Routing Connection Factory”.
"Fluent APIs" for building messages and/or message properties is now provided. See Section 3.4.1, “Message Builder API”.
A "Fluent API" for building listener container retry interceptors is now provided. See Section 3.15.2, “Failures in Synchronous Operations and Options for Retry”.
MessageRecoverer is provided to allow publishing
a failed message to another queue (including stack trace information in the header) when
retries are exhausted. See Section 3.15.3, “Message Listeners and the Asynchronous Case”.
Spring AMQP now using RabbitMQ 3.1.x by default (but retains
compatibility with earlier versions). Certain deprecations have
been added for features no longer supported by RabbitMQ 3.1.x -
federated exchanges and the
immediate property on
RabbitAdmin now provides an option to allow
exchange, queue, and binding declarations to continue when a declaration
fails. Previously, all declarations stopped on a failure. By setting
ignore-declaration-exceptions, such exceptions are logged (WARN),
but further declarations continue. An example where this might be useful is
when a queue declaration fails because of a slightly different
setting would normally stop other declarations from proceeding.
RabbitAdmin now provides an additional method
getQueueProperties(). This can be used to determine if a queue
exists on the broker (returns null for a non-existent queue). In addition,
the current number of messages in the queue, as well as the current number
of consumers is returned.
Previously, when using the
...sendAndReceive() methods were used
with a fixed reply queue, two custom headers were used for correlation
data and to retain/restore reply queue information. With this release, the
standard message property
correlationId is used by default,
although the user can specifiy a custom property to use instead. In addition,
replyTo information is now retained internally in the template,
instead of using a custom header.
immediate property is deprecated; users must not set this
property when using RabbitMQ 3.0.x or greater.
A Jackson 2.x
MessageConverter is now provided, along
with the existing converter that uses Jackson 1.x.
Previously, when declaring queues, exchanges and bindings, it was not possible
to define which connection factory was used for the declarations, each
RabbitAdmin would declare all components using
Starting with this release, it is now possible to limit declarations to specific
RabbitAdmin instances. See Section 3.8.1, “Conditional Declaration”.
Facilities are now provided for using Spring Remoting techniques, using AMQP as the transport for the RPC calls. For more information see Section 3.7.2, “Spring Remoting with AMQP”
Several users have asked for the underlying client connection factory's
property to be exposed on the Spring AMQP
CachingConnectionFactory. This is
now available; previously, it was necessary to configure the AMQP client factory as
a separate bean and provide a reference to it in the
Spring-AMQP is now built using gradle.
Adds support for publisher confirms and returns.
Adds support for HA queues, and broker failover.
Adds support for Dead Letter Exchanges/Dead Letter Queues.