Merge pull request #1047 from essobedo/AMQ-8611/describe-message-size-limit-init-param

[AMQ-8611] Describe message size limit init parameter
This commit is contained in:
JB Onofré 2023-09-09 07:17:00 +02:00 committed by GitHub
commit 6236faccec
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 18 additions and 0 deletions

View File

@ -68,6 +68,15 @@
<param-value>consumer.prefetchSize=1</param-value> <param-value>consumer.prefetchSize=1</param-value>
</init-param> </init-param>
--> -->
<!--
Uncomment this parameter if you plan to change the default max size of a message over REST. By default, it is set
to 100,000. Set it to -1 to disable the limitation but be aware that your AMQ instance could run out of memory if
the message is too big. See https://issues.apache.org/jira/browse/AMQ-8029 for more details.
<init-param>
<param-name>maxMessageSize</param-name>
<param-value>-1</param-value>
</init-param>
-->
</servlet> </servlet>
<!-- the queue browse servlet --> <!-- the queue browse servlet -->

View File

@ -35,6 +35,15 @@
<param-value>consumer.prefetchSize=1</param-value> <param-value>consumer.prefetchSize=1</param-value>
</init-param> </init-param>
--> -->
<!--
Uncomment this parameter if you plan to change the default max size of a message over REST. By default, it is set
to 100,000. Set it to -1 to disable the limitation but be aware that your AMQ instance could run out of memory if
the message is too big. See https://issues.apache.org/jira/browse/AMQ-8029 for more details.
<init-param>
<param-name>maxMessageSize</param-name>
<param-value>-1</param-value>
</init-param>
-->
</servlet> </servlet>
<!-- AMQ-9239 jakarta - jolokia does not support jakarta <!-- AMQ-9239 jakarta - jolokia does not support jakarta