<div>Hi Alexis<br></div><div>� �thanks, I think Im getting a better understanding now. Initially I wanted to look at auto requeueing for circumstances when my client subscribing to events went down or got disconnected. Now my understanding is that in those cases, messages get auto requeued.</div>
<div>� � However, if I choose not to autoack, then it looks like the responsibility of requeuing a client, forcing a time delay on the delivery and also maybe forcing a limit on the number of passes through the queue is going to have to become subscriber responsibility. I was hoping to handle that as a configuration on the queue itself outside of code, but I guess that isn't possible.</div>
<div><br></div><div>(the use case we have requires us to make sure that every message is processed as far as possible. Meaning actual failures and successes are sent onward, but failures for technical reasons require us to try again later, by which time the technical issue might have been resolved).</div>
<div><br></div><div>Im taking a look now at the task management systems now.</div><div><br></div><div>Please do describe the other ways of forcing a requeue, I'd love to know what my options are.</div><br><div class="gmail_quote">
On Wed, Dec 30, 2009 at 4:34 AM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis.richardson@gmail.com">alexis.richardson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Vishnu<br>
<br>
I am not the best person to answer this question, but I can tell you<br>
that your behaviour can be achieved without requiring timers.<br>
<br>
Assuming you are unwilling to simply close the channel and force the<br>
requeue, then:<br>
<br>
1. You could explicitly requeue by re-publishing the message. �No need<br>
to use acks here.<br>
<br>
2. You could look at what one of the many task management systems do.<br>
For example celery or quebert.<br>
<br>
<a href="http://ask.github.com/celery/introduction.html" target="_blank">http://ask.github.com/celery/introduction.html</a><br>
<a href="http://bytebucket.org/adroll/quebert/" target="_blank">http://bytebucket.org/adroll/quebert/</a><br>
<br>
Or look at the list here: <a href="http://delicious.com/alexisrichardson/rabbitmq+work" target="_blank">http://delicious.com/alexisrichardson/rabbitmq+work</a><br>
<br>
3. Other ways to force a requeue. �I am not going to try and describe<br>
these yet, in case I say something misleading.<br>
<br>
Let me know what you think.<br>
<font color="#888888"><br>
alexis<br>
</font><div><div class="h5"><br>
<br>
<br>
On Tue, Dec 29, 2009 at 8:34 PM, vishnu <<a href="mailto:pathsny@gmail.com">pathsny@gmail.com</a>> wrote:<br>
> Adding back to the list, sorry stupid email client.<br>
><br>
> would anyone know how this decision is made? When unacked messages get<br>
> requeued to be sent? I know it happens if the client disconnects, but does<br>
> it also happen on rollback?<br>
> Im trying to setup a system whereby if my subscriber picks up an item from<br>
> the queue and for some reason is unable to handle it, the item gets readded<br>
> to the queue<br>
><br>
> On Tue, Dec 29, 2009 at 8:36 PM, Alexis Richardson<br>
> <<a href="mailto:alexis.richardson@gmail.com">alexis.richardson@gmail.com</a>> wrote:<br>
>><br>
>> Vishnu<br>
>><br>
>> On Tue, Dec 29, 2009 at 2:57 PM, vishnu <<a href="mailto:pathsny@gmail.com">pathsny@gmail.com</a>> wrote:<br>
>> > hi, sorry Im a bit confused. But the behavior of moving the message from<br>
>> > the<br>
>> > unacknowledge queue to the ready queue is already a part of rabbitmq.<br>
>><br>
>> In what way?<br>
>><br>
>><br>
>> > There<br>
>> > must be some magic constant somewhere which governs this musn't there?<br>
>><br>
>> If there were then it need not be time-based.<br>
>><br>
>> alexis<br>
>><br>
>><br>
>> > On Tue, Dec 29, 2009 at 7:18 PM, Alexis Richardson<br>
>> > <<a href="mailto:alexis.richardson@gmail.com">alexis.richardson@gmail.com</a>> wrote:<br>
>> >><br>
>> >> Vishnu<br>
>> >><br>
>> >> On Tue, Dec 29, 2009 at 4:37 AM, vishnu <<a href="mailto:pathsny@gmail.com">pathsny@gmail.com</a>> wrote:<br>
>> >> > Hi<br>
>> >> > � � I'm trying to use rabbitmq for an web application thats close to<br>
>> >> > synchronous. The main reason I'm looking at rabbitmq is for the<br>
>> >> > reliability<br>
>> >> > and transactionality. The idea is for the webapplication to pump<br>
>> >> > messages<br>
>> >> > into the queue and for a down stream application to subscribe in<br>
>> >> > acknowledgement mode and for each message start a transaction,<br>
>> >> > attempt<br>
>> >> > to<br>
>> >> > process the message and if it fails for technical reasons, to<br>
>> >> > rollback<br>
>> >> > the<br>
>> >> > transaction.<br>
>> >><br>
>> >> OK.<br>
>> >><br>
>> >><br>
>> >> > However, I would like to be able to configure the time for non-acked<br>
>> >> > messages to get requeued to be picked up. Where can this be done?<br>
>> >><br>
>> >> This and other 'time based' behaviours are frequently requested, but<br>
>> >> *alas* are not yet built-in to RabbitMQ.<br>
>> >><br>
>> >> However, don't give up. �You could create a consumer (in any language)<br>
>> >> which managed this for you, eg enforcing a disconnect after some time<br>
>> >> has passed. �Or, if you are feeling brave you could create a plugin to<br>
>> >> do this 'inside the broker'. �Plugins have to be written in erlang.<br>
>> >><br>
>> >> I hope that helps. �Perhaps the list will have more immediately useful<br>
>> >> suggestions.<br>
>> >><br>
>> >> Cheers,<br>
>> >><br>
>> >> alexis<br>
>> >><br>
>> >><br>
>> >><br>
>> >> > thanks<br>
>> >> > Vishnu<br>
>> >> > _______________________________________________<br>
>> >> > rabbitmq-discuss mailing list<br>
>> >> > <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
>> >> > <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
>> >> ><br>
>> >> ><br>
>> ><br>
>> ><br>
><br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
><br>
</div></div></blockquote></div><br>