[
https://issues.apache.org/jira/browse/AMQ-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954605#comment-17954605
]
Matt Pavlovich commented on AMQ-9716:
-------------------------------------
Good catch, thank you for the bug report.
> maxMessageSize behavior changed for value -1 (since 5.19.0)
> -----------------------------------------------------------
>
> Key: AMQ-9716
> URL: https://issues.apache.org/jira/browse/AMQ-9716
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, Connector
> Affects Versions: 5.19.0
> Reporter: Bruno Köferli
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: RESTful
> Fix For: 6.2.0, 5.19.1, 6.1.7
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In RESTful API the behavior of maxMessageSize with value -1 has changed/is
> buggy. As documented the message size limit should be disabled with this
> value. But since version 5.19.0 this behavior does not work anymore.
> The bug was introduced with commit [[AMQ-9519] Remove runtime usage of
> commons-io - apache/activemq@8c12033 -
> GitHub|https://github.com/apache/activemq/commit/8c12033261e097503851b30fbf6a8ce302e6f616].
> Little side note: Also with this commit a hard coded limit of
> Integer.MAX_VALUE was introduced, which is not documented. I guess that this
> limit is not really an issue for anyone - at least not for us.
> A fix must be applied in two places:
> *
> [https://github.com/apache/activemq/blob/main/activemq-web/src/main/java/org/apache/activemq/web/MessageServletSupport.java#L362]
> *
> [https://github.com/apache/activemq/blob/main/activemq-web/src/main/java/org/apache/activemq/web/MessageServletSupport.java#L403]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
