Thats perfectly fine though. The issue I am facing has more to do with unacknowledged messages disappearing. It has nothing to do with the firing mechanism associated with it which is handled by celery in memory. I just need to understand what is happening with the rabbitmq unacknowledged messages that seem to be effectively disappearing from time to time.�<div>
<br></div><div>I think it has something to do with memory, but I can't be sure, I really dont know how rabbitmq handles these things internally.�</div><div><br></div><div>--</div><div>Mahdi</div><div><br><div class="gmail_quote">
On Fri, Jan 4, 2013 at 10:42 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 04/01/13 15:37, Mahdi Yusuf wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So you think celery is pull messages off the queue and celery isn't<br>
processing them?<br>
</blockquote>
<br></div>
I have no idea, but scheduled tasks aren't a native RabbitMQ feature.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Mahdi Yusuf</div>
</div>