[rabbitmq-discuss] Intermittent failure connecting to RabbitMQ

[Peter Soukalopoulos]

Hi Brett,

 

You're spot on with the file descriptors. There's a leak in a new component
that we did not have running originally. I looked at the open file handles
in the erl.exe service and can clearly see that number growing.

 

I've stopped the offending process and the file handles is now ok and
RabbitMQ continues to work. Yay!

 

I'll upgrade to 2.8 shortly after I fix the leak.

 

Thanks again for your pointers which have been most helpful.

 

Regards,

Peter

 

Peter Soukalopoulos 
Development Team Leader | GreenButton Limited | www.greenbutton.com
<http://www.greenbutton.com/> 
Level 13, Simpl House, 40 Mercer Street, Wellington, New Zealand 
Mobile: +64 22 632 5023| peter.soukalopoulos at greenbutton.com | Skype:
psoukal | HQ: +644 499 0424

Description: Description: GreenButton_words_small               Description:
cid:image003.jpg at 01CC4E01.BA075BC0
This message contains confidential information, intended only for the
person(s) named above, which may also be privileged. Any use, distribution,
copying or disclosure by any other person is strictly prohibited. In such
case, you should delete this message and kindly notify the sender via reply
e-mail. Please advise immediately if you or your employer does not consent
to Internet e-mail for messages of this kind.

 

From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Brett
Cameron
Sent: Wednesday, 7 November 2012 1:07 p.m.
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Intermittent failure connecting to RabbitMQ

 

Peter,

It's unfortunate that you've dropped back to 2.7.1 as you get better
visibility via rabbitmqctl of available descriptors with 2.8.*. If you fire
up an Erlang shell and enter "erlang:system_info(check_io).", you'll see
max_fds listed in the output. I've not got a Windows server readily
available to check, but my guess is the default limit is something like 256.


ERL_MAX_PORTS is set as a Windows environment variable.

In your original post the following message makes me thing that you'd hit
the fd limit. 

=INFO REPORT==== 6-Nov-2012::16:30:13 ===

    alarm_handler: {clear,file_descriptor_limit}

This message is logged when the situation is cleared, so somewhere higher up
in the log there should be a corresponding "alarm_handler:
{set,{file_descriptor_limit,[]}}" or some such message.