POJO listeners can be annotated with @RabbitListener, enabled
by @EnableRabbit or <rabbit:annotation-driven />.
Spring Framework 4.1 is required for this feature.
See Section 3.5.3, “Annotation-driven listener endpoints” for more information.
A new RabbitMessagingTemplate is provided to allow users
to interact with RabbitMQ using spring-messaging Messages.
It uses the RabbitTemplate internally which can be configured
as normal.
Spring Framework 4.1 is required for this feature.
See Section 3.3.3, “Messaging integration” for more information.
1.3.5 introduced the missingQueuesFatal property on the
SimpleMessageListenerContainer. This is now
available on the listener container namespace element.
See Section 3.11, “Message Listener Container Configuration”.
The confirm method on this interface has an additional
parameter cause. When available, this parameter will
contain the reason for a negative acknowledgement (nack).
See Section 3.3.2, “Publisher Confirms and Returns”.
A factory bean is now provided to create the underlying RabbitMQ
ConnectionFactory used by the
CachingConnectionFactory. This enables
configuration of SSL options using Spring's dependency
injection.
See Section 3.2.1, “Configuring the Underlying Client Connection Factory”.
The CachingConnectionFactory now allows
the connectionTimeout to be set as a property
or as an attribute in the namespace. It sets the property
on the underlying RabbitMQ ConnectionFactory
See Section 3.2.1, “Configuring the Underlying Client Connection Factory”.
The Logback org.springframework.amqp.rabbit.logback.AmqpAppender
has been introduced. It provides similar options like
org.springframework.amqp.rabbit.log4j.AmqpAppender.
For more info see JavaDocs of these classes.
The Log4j AmqpAppender now supports the
deliveryMode property (PERSISTENT or
NON_PERSISTENT, default: PERSISTENT).
Previously, all log4j messages were PERSISTENT.
The appender also supports modification of the Message
before sending - allowing, for example, the addition of custom
headers. Subclasses should override the
postProcessMessageBeforeSend().
The listener container now, by default, redeclares any missing queues during startup.
A new auto-declare attribute has been added to the
<rabbit:listener-container> to prevent these redeclarations.
See the section called “'auto-delete' Queues”.
The mandatoryExpression and sendConnectionFactorySelectorExpression
and receiveConnectionFactorySelectorExpression SpEL
Expressions properties
have been added to the RabbitTemplate.
The mandatoryExpression is used to evaluate a mandatory
boolean value against each request message, when a ReturnCallback is in use.
See Section 3.3.2, “Publisher Confirms and Returns”.
The sendConnectionFactorySelectorExpression and
receiveConnectionFactorySelectorExpression are used when an
AbstractRoutingConnectionFactory is provided, to determine the
lookupKey for the target ConnectionFactory at runtime on
each AMQP protocol interaction operation.
See Section 3.2.3, “Routing Connection Factory”.
A SimpleMessageListenerContainer can be configured with a routing
connection factory to enable connection selection based on the queue names.
See Section 3.2.3, “Routing Connection Factory”.
The recoveryCallback property has been added to be used in the
retryTemplate.execute().
See Section 3.3.1, “Adding Retry Capabilities”.
This exception is now a subclass of AmqpException; if you have code like
the following:
try { template.convertAndSend("foo", "bar", "baz"); } catch (AmqpException e) { ... } catch (MessageConversionException e) { ... }
The second catch block will no longer be reachable and needs to be moved above the catch-all
AmqpException catch block.
Spring AMQP is now compatible with the RabbitMQ 3.4, including direct reply-to; see Section 1.1.1, “Compatibility” and Section 3.7.1, “RabbitMQ Direct reply-to” for more information.
The ContentTypeDelegatingMessageConverter has been introduced to select
the MessageConverter to use, based on the contentType
property in the MessageProperties. See Section 3.6, “Message Converters”
for more information.
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”.
The 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 binding element
of 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 Queue or Exchange.
Users wishing to bind with an empty string routing key need to specify
key="".
The AmqpTemplate now
provides several synchronous receiveAndReply methods. These are implemented
by the RabbitTemplate.
For more information see Section 3.5, “Receiving messages”.
The 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 Connections
and their Channels instead of using a single
connection and caching just Channels. See Section 3.2, “Connection and Resource Management”.
The <exchange>'s <binding> now supports parsing of
the <binding-arguments> sub-element. The <headers-exchange>'s
<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”.
A new SimpleRoutingConnectionFactory has been introduced,
to allow configuration of ConnectionFactories mapping to determine
the target ConnectionFactory to use at runtime.
See Section 3.2.3, “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”.
This new 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”.
A default ConditionalRejectingErrorHandler has been added
to the listener container. This error handler detects message conversion problems
(which are fatal) and instructs the container to reject the message to prevent
the broker from continually redelivering the unconvertible message.
See Section 3.9, “Exception Handling”.
The SimpleMessageListenerContainer now has a property
missingQueuesFatal (default true). Previously,
missing queues were always fatal.
See Section 3.11, “Message Listener Container Configuration”.
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
the RabbitTemplate.
The 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 ttl
setting would normally stop other declarations from proceeding.
The 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,
nested replyTo information is now retained internally in the template,
instead of using a custom header.
The 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
its connection.
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.3, “Spring Remoting with AMQP”
Several users have asked for the underlying client connection factory's requestedHeartBeats
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 CachingConnectionFactory.
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.