summaryrefslogtreecommitdiff
path: root/docs/rabbitmq.config.example
diff options
context:
space:
mode:
authorMichael Klishin <michael@clojurewerkz.org>2017-10-20 21:25:06 +0300
committerMichael Klishin <michael@clojurewerkz.org>2017-10-20 21:25:06 +0300
commit7db615949f34162f9b283b63cae528cd25d21317 (patch)
tree0e088b9ea4ff2158874a1cf82d6cad67a09d2db9 /docs/rabbitmq.config.example
parente6448b2170fcc48cc6275f917ac025e13c43ddf2 (diff)
downloadrabbitmq-server-git-7db615949f34162f9b283b63cae528cd25d21317.tar.gz
Add rabbit.connection_max to rabbitmq.config.example
Diffstat (limited to 'docs/rabbitmq.config.example')
-rw-r--r--docs/rabbitmq.config.example19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/rabbitmq.config.example b/docs/rabbitmq.config.example
index fe0f7b04cd..990ffccc09 100644
--- a/docs/rabbitmq.config.example
+++ b/docs/rabbitmq.config.example
@@ -218,6 +218,25 @@
%%
%% {channel_max, 0},
+ %% Set the max permissible number of client connections to the node.
+ %% `infinity` means "no limit".
+ %%
+ %% This limit applies to client connections to all listeners (regardless of
+ %% the protocol, whether TLS is used and so on). CLI tools and inter-node
+ %% connections are exempt.
+ %%
+ %% When client connections are rapidly opened in succession, it is possible
+ %% for the total connection count to go slightly higher than the configured limit.
+ %% The limit works well as a general safety measure.
+ %%
+ %% Clients that are hitting the limit will see their TCP connections fail or time out.
+ %%
+ %% Introduced in 3.6.13.
+ %%
+ %% Related doc guide: http://www.rabbitmq.com/networking.html.
+ %%
+ %% {connection_max, infinity},
+
%% TCP socket options.
%%
%% Related doc guide: http://www.rabbitmq.com/networking.html.