[erlang-questions] Ho to keep-alive inactive RabbitMQ connections?
Fri Dec 14 18:30:21 CET 2012
Here is another a little bit optimized example of RabbitMQ connection
Line 69: add erlang:monitor
Lines 43, 47: Here you get 'DOWN' from failed link
Line 118: Here I restart the link. (of course it could be
erlang:send_after/3, but since link is already down timer:sleep/1 also
I hope it will help somehow to the great team of RabbitMQ
On Fri, Dec 14, 2012 at 9:15 PM, Tim Watson <watson.timothy@REDACTED>wrote:
> Rabbit connections can be set to use AMQP heartbeats, which provide
> something similar to keep-alive but also let's the broker deal explicitly
> with disappearing clients efficiently.
> There is the issue of automatically reconnecting, which the native
> (erlang) client doesn't do. There are several libraries that add similar
> support, one of which is written by Max from the sounds of things. This can
> be quite involved if you're using exclusive/auto-delete objects so I'd
> suggest looking at some of the tools out there before rollin your own, even
> if it's just instructional to do so.
> Do you have code shared anywhere Max? If so we could add it to the tools
> page on rabbitmq.com, unless it's there already? let me know.
> Staff Engineer
> On 14 Dec 2012, at 17:00, Max Bourinov <bourinov@REDACTED> wrote:
> Hi Den,
> RabbitMQ works very well. My code also included auto-recovery
> functionality and some other useful stuff. Please describe your problem and
> I will try to provide you with detailed solution.
> Best regards,
> On Fri, Dec 14, 2012 at 8:17 PM, Денис None <jobforme17@REDACTED> wrote:
>> Hi Max,
>> Have you overcome the "[erlang-questions] Ho to keep-alive inactive
>> RabbitMQ connections?" issue. If so, kindly advise me on this problem.
>> Thank you in advance.
>> Best Regards,
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions