[rabbitmq-discuss] C client questions . . .

Fri Aug 17 15:40:21 BST 2012

Jeff;

Handshake timeout? I think that's what happens when the client opens a
socket (using amqp_open_socket) to the broker and doesn't complete the
handshake process (calling amqp_login) in a certain amount of time.  The
timeout is something set on the broker.

I could imagine this sort of thing happening if for whatever reason the
handshake was delayed, or you open a bunch of sockets to the broker without
doing the handshake (calling amqp_login).  Other reasons why this could be
happening:
- The broker is too busy (I/O or CPU) to complete the handshake in enough
time (maybe you have a bunch of clients trying to connect at the same time?)
- There is a serious amount of network traffic preventing your clients from
getting to the broker.
- Something on the client side is really slowing down the handshake process

Going to CC the rabbitmq-discuss list see if they have any ideas.

-Alan

On Fri, Aug 17, 2012 at 12:13 AM, Jeff Markham <jmarkham at vmware.com> wrote:

> Hi Alan,
>
> Was wondering if you might know of any circumstance that might cause the
> the client to peg the broker.  At ~130 client connections, we see
>
> =ERROR REPORT==== 14-Aug-2012::16:04:33 ===
> closing AMQP connection <0.8196.3> (1.1.1.1:63114 -> 2.2.2.2:5671):
> {handshake_timeout,handshake}
>
> in the logs and over and over until it consumes the entire memory of the
> box.  Doesn't happen always but enough that we can't figure out what might
> be causing this.
>
> Thanks for everything.
>
> https://github.com/rabbitmq/rabbitmq-c
>
> Jeff Markham
> Senior Systems Engineer
> vFabric Cloud Application Platform
> VMware
> (949) 385-3806
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120817/594d49a1/attachment.htm>