Why not running pika's IOLoop in a thread and communicate with it with python queues ?<div><br></div><div>You can then leave heartbeats on, and the main thread could continue processing your tasks.</div><div><br></div>
<div>Raphael<br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 1:00 PM, 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 08/03/13 21:52, Nishanth Babu Achuthan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Typical job processing time is 24 hours. I set up heartbeat_interval =<br>
432000 (5 days) . When I tried this earlier, connection dropped off<br>
approximately after 10 mins.<br>
<br>
I tried with heartbeat=0 and looks like it is working. I find the<br>
connection active after 90 minutes since the message processing started.<br>
</blockquote>
<br></div>
Setting heartbeat=0 when connections are expected to be be idle for many hours seems less than ideal. The risk of the connection getting nuked by some idle-timeout on a firewall etc must be fairly high with such a setup.<br>
<br>
Gavin, is there no better way to deal with this? Could an app perhaps invoke some pika API function at reasonably regular intervals that would deal with any inbound/outbound heartbeats received/due since the last invocation?<br>
<br>
Regards,<br>
<br>
Matthias.<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>