From 66a44fa157f2ab3f68e9894f13a0f4eb4ff71b80 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Thu, 19 Jan 2017 10:53:56 +0300 Subject: [PATCH] Correct and expand rabbitmqctl(1) examples for vhost limits --- docs/rabbitmqctl.1.xml | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml index 32dc43845a..ec3bbde75c 100644 --- a/docs/rabbitmqctl.1.xml +++ b/docs/rabbitmqctl.1.xml @@ -1328,15 +1328,28 @@ JSON term. In most shells you are very likely to need to quote this. - Recognised limits: max-connections (0 means "no limit"). + Recognised limits: max-connections, max-queues. Use a negative value to specify "no limit". For example: - rabbitmqctl set_vhost_limits -p qa_env '{"max-connections": 1024}' + rabbitmqctl set_vhost_limits -p qa_env '{"max-connections": 64}' This command limits the max number of concurrent connections in vhost qa_env - to 1024. + to 64. + + rabbitmqctl set_vhost_limits -p qa_env '{"max-queues": 256}' + + This command limits the max number of queues in vhost qa_env + to 256. + + rabbitmqctl set_vhost_limits -p qa_env '{"max-connections": -1}' + + This command clears the max number of connections limit in vhost qa_env. + + rabbitmqctl set_vhost_limits -p qa_env '{"max-connections": 0}' + + This command disables client connections in vhost qa_env.