<html><head><base href="x-msg://267/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I do something very similar with retries when operations triggered by a message fail. On failure, I write the message, exchange, routing key, and header information to a Riak server. A scheduled job comes along later and removes these messages from Riak and re-publishes them. The process may or may not be repeated N times, depending on whether later runs were successful or not.<div><br></div><div>I don't know if Rabbit has this functionality built-in, but having a "delayed delivery" would be awesome.</div><div><br></div><div>The only other way to do it is to actually publish and deliver a message, but have the consumer delay acting on it. I felt like a more reliable solution is to persist a message to a NoSQL store where I can delete, retrieve, or replay the message as many times as I want to. It adds another component to the mix, but I use Riak for things like this anyway, so why not? :)<br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Georgia; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div><br>Jon Brisbin</div><div>Portal Webmaster</div><div>NPC International, Inc.</div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Sep 27, 2010, at 8:54 AM, Darren Lee wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Georgia; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div lang="EN-GB" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; ">Hi everyone,<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><br>I�m looking for advice on the best way to schedule messages to be received after a certain time. I have a system where files get published out to a CDN and then the system needs to verify the files were propagated out correctly, this can sometimes take hours. I would like my subscriber to see a message, check for completion and if not put the message back on the queue to be dealt with in X minutes time.<o:p></o:p></div><div style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; "><br>Thanks for any help,<br>Darren<o:p></o:p></div></div>_______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" style="color: blue; text-decoration: underline; ">rabbitmq-discuss@lists.rabbitmq.com</a><br><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" style="color: blue; text-decoration: underline; ">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br></div></span></blockquote></div><br></div></body></html>