[rabbitmq-discuss] RabbitMQ actively refuses connections after connectity issues

James Carr james.r.carr at gmail.com
Fri Aug 5 21:56:05 BST 2011

Is there anyway on the server side to limit the max number of
connections a single user or ip can make? We had the same issue
described above due to some erronous consumer logic deployed in one of
the applications using RabbitMQ. It quickly took up all the
connections and never closed them, which in turn impacted the other
applications that used that server. :(


On Thu, Aug 4, 2011 at 6:07 AM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
> Alfonso,
> On 02/08/11 15:36, Alfonso Pantoja wrote:
>> By the way  Since we are using RequestedHeartbeat feature is it possible
>> to open a connection to rabbit and not use it anymore without being
>> disconnected?
>> (setting RequestedHeartbea with a value > 0 is enough or additional code
>> is needed?)
> Correct. Setting RequestedHeartbeat enables logic in the client library that
> automatically sends out heartbeat frames at the configured interval whenever
> no other data is being transmitted.
> Regards,
> Matthias.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list