Fix example value for max-message-size (#4792)

* Fix example value for max-message-size @npepinpe once told me to use `zeebe.client.message.max-message-size=4194304`, which sounds like the default value and seems to be in bytes. If we use a too small example value, users may think the value is in megabytes. Obviously, we could also just document the unit but even then 3 bytes is likely not a workable value. * backport --------- Co-authored-by: Christina Ausley <christina.ausley@camunda.com>
camunda · Dec 23, 2024 · 9f20060 · 9f20060
1 parent 19bba98
commit 9f20060
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/apis-tools/spring-zeebe-sdk/configuration.md b/docs/apis-tools/spring-zeebe-sdk/configuration.md
@@ -275,7 +275,7 @@ A custom maxMessageSize allows the client to receive larger or smaller responses
 camunda:
   client:
     zeebe:
-      max-message-size: 3
+      max-message-size: 4194304
 ```
 
 ### Request timeout

diff --git a/versioned_docs/version-8.6/apis-tools/spring-zeebe-sdk/configuration.md b/versioned_docs/version-8.6/apis-tools/spring-zeebe-sdk/configuration.md
@@ -275,7 +275,7 @@ A custom maxMessageSize allows the client to receive larger or smaller responses
 camunda:
   client:
     zeebe:
-      max-message-size: 3
+      max-message-size: 4194304
 ```
 
 ### Request timeout