[rabbitmq-discuss] Question about Scheduled Message Delivery

Daniel W. Burke dburke at addictmud.org
Wed Jun 18 00:41:04 BST 2014

We got around this by implementing a temporary queue that set its
x-dead-letter-routing-key to the queue we want it delivered to, and then
use a combination of x-expires and message-ttl to have the message
delivered to the "real" queue at the desired time, and then the queue
deletes itself effectively cleaning things up all nice and neat.

The downside is that you are really using one queue per message that is
delayed, it doesn't seem to be a problem for us, but YMMV.

We used perl, but here is where we got the idea...



On Tue, Jun 17, 2014 at 6:40 PM, Michael Klishin <mklishin at gopivotal.com>

> On 17 June 2014 at 23:58:00, Manish Ranade (manish.ranade at gmail.com)
> wrote:
> > > We have an application that allows users to submit a request
> > that needs to be processed on a specific time and date in the future.
> > If there was no constraint of time and date, we would have put the
> > request in a queue and have the consumer pick the request one by
> > one and process them. However, considering my scenario—
> >
> > Is it possible to publish a message to be consumed at later stage?
> RabbitMQ does not perform this kind of scheduling. It can be extended to do
> this (by implementing a custom exchange in Erlang) but it remains to be
> seen
> how good that approach will actually work.
> --
> MK
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140617/1e75b814/attachment.html>

More information about the rabbitmq-discuss mailing list