[rabbitmq-discuss] maximum connections

[Alexandru Scvorţov]

> I'm testing out a new rabbitMQ system and noticed that the system seems to stop accepting new connections after around 830 get opened.  Can anyone tell me what would cause it to stop at that point? 

It ran out of socket descriptors probably (or was getting close to the
limit and the internal descriptor limiter kicked in).  On my system,
this limit is 829, by default, so this is likely the cause.

This is calculated as a fixed fraction of the file descriptor limit.

> The system ulimit on open files is 4096 (soft & hard) and the rabbitMQ user isn't anywhere near using that many.  Is there anything else that could be responsible for this limit?

Huh.  Are you sure?  A 830 socket limit corresponds to a 1024 file
descriptor limit.

Try enabling the management plugin to see if what the limits are what
you think they are (the overview page gives a breakdown of the limits
RabbitMQ knows about).

What is the output of `ulimit -a`?  What happens if you do a `ulimit -n
4096` in the shell before starting rabbitmq-server in the same shell?
That should increase the maximum number of connection to 3594.

Cheers,
Alex

On Mon, Oct 24, 2011 at 09:04:38PM -0700, Michael Barrett wrote:
> I'm testing out a new rabbitMQ system and noticed that the system seems to stop accepting new connections after around 830 get opened.  Can anyone tell me what would cause it to stop at that point?  The system ulimit on open files is 4096 (soft & hard) and the rabbitMQ user isn't anywhere near using that many.  Is there anything else that could be responsible for this limit?
> 
> Thanks!
> 
> --
> Michael Barrett
> loki77 at gmail.com
> 
> 
> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss