<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">You could resend non acked messages
without closing connection <br>
by basic.recover. Also you could possibly apply timeout to the
messages <br>
in companion of dead-lettering (in your case dead-lettering to the
same <br>
queue should be just right choice). This would redeliver messages
after <br>
their expiration. <br>
<br>
Does my answer cover your needs?<br>
<br>
W dniu 2012-07-19 23:11, Prashanth pisze:<br>
</div>
<blockquote
cite="mid:CAE8G+yQWNjLaNRRTL-2Tqj_F7air0VsWheU571SimpJrCmoxqg@mail.gmail.com"
type="cite">Hi,
<div><br>
</div>
<div>My test case.
<div><br>
</div>
<div>I have a consumer, with no_ack =>0, prefetch_count is
default, consumer receives messages, even if previous messages
are not acknowledge.</div>
<div>If the message is never acknowledge or ack message is lost
in transit and if consumer never goes down, This message is
never acknowledged or is resent again, its in the queue
forever. I don't want to timeout the message.</div>
<div>Instead I want the message to resend after
a specified timeout may be to the same consumer.</div>
<div><br>
</div>
<div>Is there a way to do this.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rabbitmq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<a class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>