[rabbitmq-discuss] Rabbit connections dying from protected enviornment

Jason McIntosh mcintoshj at gmail.com
Fri Oct 25 14:54:11 BST 2013

We hit the same kinda things with the F5's.  The F5's work more as a proxy
and not a router so the basic TCP FastL4 connection profile does a reset on
an idle connection at a default of 5 minutes.  We added a new F5 FastL4
profile for 10 minute resets and upgraded to the rabbit 3 release that
added heartbeat support, and a lot of our issues went away.  Note you'd
only see the issue if there was 0 traffic going through, e.g. no messages
being published.  We have a lot of servers set to shovel to a centralized
location and some of our remote nodes weren't publishing regularly - turns
out we saw very regular (5 minute intervals) disconnects on the log files.

I would recommend tweaking your connection settings.  For example, the f5's
don't have a default protocol handler for AMQP, so we had  to use TCP


On Wed, Oct 16, 2013 at 10:21 AM, Ganann, Kale <KGanann at kroll.com> wrote:

> They hadn't had their heartbeats set correctly.  We've updated the broker
> to push a heartbeat every four minutes from our end of the connection.
>  Thanks for your help!
> Thanks,
> Kale
> -----Original Message-----
> From: Emile Joubert [mailto:emile at rabbitmq.com]
> Sent: Friday, October 11, 2013 11:11 AM
> To: Discussions about RabbitMQ
> Cc: Ganann, Kale
> Subject: Re: [rabbitmq-discuss] Rabbit connections dying from protected
> enviornment
> Hi Kale,
> On 11/10/13 16:54, Ganann, Kale wrote:
> > If we try to go past the VIP straight to a node, it fails outright
> In what way exactly does it fail? What do the broker logfiles say?
> What happens if you shut down all but one of the broker nodes?
> > Thus the main issue is what is the client seeing that causing it to
> > restart the connection.
> That's hard to guess without knowing the logic of the client or it's
> network input.
> > Any ideas on what in that sequence could be hosing us up?
> It should be possible to provide better feedback if you can supply the
> output of connecting the client via the tracer:
> http://www.rabbitmq.com/javadoc/com/rabbitmq/tools/Tracer.html
> -Emile
> This communication contains information that is confidential,
> proprietary in nature, and may also be attorney-client privileged
> and/or work product privileged. It is for the exclusive use of the
> intended recipient(s). If you are not the intended recipient(s) or
> the person responsible for delivering it to the intended
> recipient(s), please note that any form of dissemination,
> distribution or copying of this communication is strictly
> prohibited and may be unlawful. If you have received this
> communication in error, please immediately notify the sender by replying
> to this message and delete this email immediately. Thank you for your
> cooperation.
> Please be advised that neither Altegrity, its affiliates, its employees
> or agents accept liability for any errors, omissions or damages
> caused by delays of receipt or by any virus infection in this
> message or its attachments, or which may otherwise arise as a
> result of this e-mail transmission.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Jason McIntosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131025/e202de46/attachment.htm>

More information about the rabbitmq-discuss mailing list