Adding back to the list, sorry stupid email client.<br><div><br></div><div>would anyone know how this decision is made? When unacked messages get requeued to be sent? I know it happens if the client disconnects, but does it also happen on rollback?</div>
<div><br></div><div>Im trying to setup a system whereby if my subscriber picks up an item from the queue and for some reason is unable to handle it, the item gets readded to the queue</div><div><br></div><div><br></div><div class="gmail_quote">
On Tue, Dec 29, 2009 at 8:36 PM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis.richardson@gmail.com" target="_blank">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>
<div><br>
On Tue, Dec 29, 2009 at 2:57 PM, vishnu <<a href="mailto:pathsny@gmail.com" target="_blank">pathsny@gmail.com</a>> wrote:<br>
> hi, sorry Im a bit confused. But the behavior of moving the message from the<br>
> unacknowledge queue to the ready queue is already a part of rabbitmq.<br>
<br>
</div>In what way?<br>
<div><br>
<br>
> There<br>
> must be some magic constant somewhere which governs this musn't there?<br>
<br>
</div>If there were then it need not be time-based.<br>
<font color="#888888"><br>
alexis<br>
</font><div><div><br>
<br>
> On Tue, Dec 29, 2009 at 7:18 PM, Alexis Richardson<br>
> <<a href="mailto:alexis.richardson@gmail.com" target="_blank">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" target="_blank">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, attempt<br>
>> > to<br>
>> > process the message and if it fails for technical reasons, to 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" target="_blank">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>
</div></div></blockquote></div><br>