From c93cacf477deb6557e693dd016436e0d12895f54 Mon Sep 17 00:00:00 2001
From: Simon Unge <simunge@amazon.com>
Date: Fri, 24 Jan 2025 18:22:57 +0000
Subject: [PATCH] Log incorrectly claims the limit is per node, but the
 component count is over all vhost in the cluster

---
 deps/rabbit/src/rabbit_runtime_parameters.erl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/deps/rabbit/src/rabbit_runtime_parameters.erl b/deps/rabbit/src/rabbit_runtime_parameters.erl
index f7851b635ee8..f919ad396900 100644
--- a/deps/rabbit/src/rabbit_runtime_parameters.erl
+++ b/deps/rabbit/src/rabbit_runtime_parameters.erl
@@ -166,10 +166,10 @@ is_within_limit(Component) ->
     case Limit < 0 orelse count_component(Component) < Limit of
        true -> ok;
        false ->
-            ErrorMsg = "Limit reached: component ~ts is limited to ~tp per node",
+            ErrorMsg = "Limit reached: component ~ts is limited to ~tp",
             ErrorArgs = [Component, Limit],
             rabbit_log:error(ErrorMsg, ErrorArgs),
-            {errors, [{"component ~ts is limited to ~tp per node", [Component, Limit]}]}
+            {errors, [{"component ~ts is limited to ~tp", [Component, Limit]}]}
     end.
 
 count_component(Component) -> length(list_component(Component)).