[rabbitmq-discuss] C client questions . . .
brett.r.cameron at gmail.com
Fri Aug 17 21:37:50 BST 2012
Also, do the failed connections always come from the same address(es)?
Could there be a dodgy piece of network kit somewhere that's causing
On Sat, Aug 18, 2012 at 8:01 AM, Brett Cameron <brett.r.cameron at gmail.com>wrote:
> I'm sure Simon or Emile will correct me if I'm wrong, but I seem to recall
> that the handshake timeout is currently hardwired in the broker to 10s. I
> think there's also a SSL timeout of 5s. I've managed to hit one or both of
> these limits when using a slow(ish) connection with SSL over the internet,
> but have never hit it on the LAN, even with the broker managing many
> thousands of simultaneous connections (all created literally one after the
> other with no delay). Do you have any more details on your configuration?
> On Sat, Aug 18, 2012 at 2:40 AM, Alan Antonuk <alan.antonuk at gmail.com>wrote:
>> 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
>> - 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
>> Going to CC the rabbitmq-discuss list see if they have any ideas.
>> 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> (22.214.171.124:63114 -> 126.96.36.199:5671):
>>> 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.
>>> Jeff Markham
>>> Senior Systems Engineer
>>> vFabric Cloud Application Platform
>>> (949) 385-3806
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss