[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435923#comment-17435923
]
arne anka commented on ARTEMIS-3535:
------------------------------------
Thanks, I am aware of the workaround, but so far the update was on my staging
server only.
Is there an estimate as to when 2.20.0 (presuming the fix included) will be
released?
BTW:
maybe the producer should be amended to also produce a {{byte}} test message?
{code:java}
./artemis producer --destination queue://unlimitedQueue --message-count 1
--byte-size 5000
{code}
I suspected {{byte}} vs {{text}} early on (since it was the most obvious
difference) and tried to check that way, but had to jump through all the hoops
with REST instead.
> management-message-attribute-size-limit = -1 does not unlimit
> -------------------------------------------------------------
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.19.0
> Reporter: arne anka
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.20.0
>
> Attachments: artemis-rest-2.19.0.war, broken_message.png, broker.xml,
> limited.jpg, rest.messaging.config.file.xml, test.xml, unlimited.jpg, web.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
> <address-setting match="#">
> ...
>
> <management-message-attribute-size-limit>-1</management-message-attribute-size-limit>
> </address-setting>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
