[rabbitmq-discuss] Keeping idle connections alive in EC2

Raphaël De GIUSTI raphael.degiusti at guardis.com
Tue Mar 12 12:29:20 GMT 2013

Why not running pika's IOLoop in a thread and communicate with it with
python queues ?

You can then leave heartbeats on, and the main thread could continue
processing your tasks.


On Mon, Mar 11, 2013 at 1:00 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 08/03/13 21:52, Nishanth Babu Achuthan wrote:
>> Typical job processing time is 24 hours. I set up heartbeat_interval =
>> 432000 (5 days) . When I tried this earlier, connection dropped off
>> approximately after 10 mins.
>> I tried with heartbeat=0 and looks like it is working. I find the
>> connection active after 90 minutes since the message processing started.
> 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.
> 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?
> Regards,
> Matthias.
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130312/78171ebc/attachment.htm>

More information about the rabbitmq-discuss mailing list