This plugin adds delayed-messaging (or scheduled-messaging) to RabbitMQ.
A user can declare an exchange with the type x-delayed-message
and
then publish messages with the custom header x-delay
expressing in
milliseconds a delay time for the message. The message will be
delivered to the respective queues after x-delay
milliseconds.
This plugin targets RabbitMQ 3.5.7 and later versions.
Install the corresponding .ez files from our Community Plugins page.
Then run the following command:
rabbitmq-plugins enable rabbitmq_delayed_message_exchange
To use the delayed-messaging feature, declare an exchange with the
type x-delayed-message
:
// ... elided code ...
Map<String, Object> args = new HashMap<String, Object>();
args.put("x-delayed-type", "direct");
channel.exchangeDeclare("my-exchange", "x-delayed-message", true, false, args);
// ... more code ...
Note that we pass an extra header called x-delayed-type
, more on it
under the Routing section.
Once we have the exchange declared we can publish messages providing a header telling the plugin for how long to delay our messages:
// ... elided code ...
byte[] messageBodyBytes = "delayed payload".getBytes("UTF-8");
Map<String, Object> headers = new HashMap<String, Object>();
headers.put("x-delay", 5000);
AMQP.BasicProperties.Builder props = new AMQP.BasicProperties.Builder().headers(headers);
channel.basicPublish("my-exchange", "", props.build(), messageBodyBytes);
byte[] messageBodyBytes2 = "more delayed payload".getBytes("UTF-8");
Map<String, Object> headers2 = new HashMap<String, Object>();
headers2.put("x-delay", 1000);
AMQP.BasicProperties.Builder props2 = new AMQP.BasicProperties.Builder().headers(headers2);
channel.basicPublish("my-exchange", "", props2.build(), messageBodyBytes2);
// ... more code ...
In the above example we publish two messages, specifying the delay
time with the x-delay
header. For this example, the plugin will
deliver to our queues first the message with the body "more delayed payload"
and then the one with the body "delayed payload"
.
If the x-delay
header is not present, then the plugin will proceed
to route the message without delay.
This plugin allows for flexible routing via the x-delayed-type
arguments that can be passed during exchange.declare
. In the example
above we used "direct"
as exchange type. That means the plugin
will have the same routing behavior shown by the direct exchange.
If you want a different routing behavior, then you could provide a
different exchange type, like "topic"
for example. You can also
specify exchange types provided by plugins. Note that this argument is
required and must refer to an existing exchange type.
Due to the "x-delayed-type"
argument, one could use this exchange in
place of other exchanges, since the "x-delayed-message"
exchange
will just act as proxy. Note that there might be some performance
implications if you do this.
For each message that crosses an "x-delayed-message"
exchange, the
plugin will try to determine if the message has to be expired by
making sure the delay is within range, ie: Delay > 0, Delay =< ?ERL_MAX_T
(In Erlang a timer can be set up to (2^32)-1 milliseconds
in the future).
If the previous condition holds, then the message will be persisted to Mnesia and some other logic will kick in to determine if this particular message delay needs to replace the current scheduled timer and so on.
This means that while one could use this exchange in place of a direct or fanout exchange (or any other exchange for that matter), it will be slower than using the actual exchange. If you don't need to delay messages, then use the actual exchange.
Mandatory flag is not supported by this exchange: we cannot be sure that at the future publishing point in time
- there is at least one queue we can route to
- the original connection is still around to send a
basic.return
to
You can disable this plugin by calling rabbitmq-plugins disable rabbitmq_delayed_message_exchange
but note that ALL DELAYED MESSAGES THAT
HAVEN'T BEEN DELIVERED WILL BE LOST.
At the moment the plugin is experimental in order to receive feedback from the community.
See the LICENSE file.