[rabbitmq-discuss] Keeping idle connections alive in EC2

[slash]

Has anyone been able to figure this out?I experience the same issue with
connections being closed at precisely the 30-minute mark after a connection
is established. I tried setting the connection parameter
*heartbeat_interval* to both zero and 3600 and also the *socket_timeout* to
1860 seconds. Acknowledging early before a long-running process does not
work either.The EC2 instances are running linux and has pika 0.9.13.



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Keeping-idle-connections-alive-in-EC2-tp25324p29107.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130826/28ad142f/attachment.htm>