[activemq-website] branch main updated: [AMQ-8412] Update doc for maxFrameSizeEnabled check

[jb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jbonofre pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 97ba49d17 [AMQ-8412] Update doc for maxFrameSizeEnabled check
     new e06a2d2bd Merge pull request #74 from mattrpav/AMQ-8412-website
97ba49d17 is described below

commit 97ba49d1719af7b3bbb25c56e126d3ffe7832563
Author: Matt Pavlovich <ma...@hyte.io>
AuthorDate: Sun Feb 6 19:24:10 2022 -0600

    [AMQ-8412] Update doc for maxFrameSizeEnabled check
---
 src/configuring-wire-formats.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/configuring-wire-formats.md b/src/configuring-wire-formats.md
index 63557a26b..863d6691f 100644
--- a/src/configuring-wire-formats.md
+++ b/src/configuring-wire-formats.md
@@ -18,6 +18,7 @@ Option|Default|Description
 `maxInactivityDuration`|`30000`|The maximum [inactivity](activemq-inactivitymonitor) duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to die. Therefore allow the broker to kill connections when they have been inactive for the configured period of time. Used by some transports to enable a keep alive heart beat feature. Inactivity monitoring is disabled when set to a value `<= 0`.
 `maxInactivityDurationInitalDelay`|`10000`|The initial delay before starting [inactivity](activemq-inactivitymonitor) checks. Yes, the word `'Inital'` is supposed to be misspelled like that.
 `maxFrameSize`|`MAX_LONG`|Maximum allowed frame size. Can help help prevent OOM DOS attacks.
+`maxFrameSizeEnabled`|`true`|Should the maxFrameSize check be verified? (since: v5.16.4)
 `sizePrefixDisabled`|`false`|Should the size of the packet be prefixed before each packet is marshaled?
 `stackTraceEnabled`|`true`|Should the stack trace of exception that occur on the broker be sent to the client?
 `tcpNoDelayEnabled`|`true`|Does not affect the wire format, but provides a hint to the peer that `TCP_NODELAY` should be enabled on the communications Socket.
@@ -41,3 +42,7 @@ ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("tcp://localhost:61
   <!-- other options... -->
 </bean>
 ```
+
+**Max Frame Size:**
+
+The maxFrameSizeEnabled check applies to both the client and server-side. The setting is _not_ transferred from the server to the client during wireformat negotiation. This allows clients and servers to configure independently (generally only for testing).