[
https://issues.apache.org/jira/browse/ARTEMIS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431126#comment-17431126
]
Gary Tully commented on ARTEMIS-3141:
-------------------------------------
It is typically the body that is large and needs to be truncated, the body,
properties etc are all ``attributes`` of the message.
I think if users want to use the webconsole as a messaging browser and see the
whole message, they need to configure the broker or the addresses to allow
that. In typical. usage, there is just way too much data to be moving between
the broker and browser/UI for the defaults to be anything other than
restrictive/conservative.
But even so, a message could be stored as a LargeMessage on the broker and it
won't be visible in the console representation.
I don't see an easy answer to "get a single full message by ID as <JSON, XML,
bytes, base64>" when the message is stored as a Large Message.
> limit the amount of data returned from jmx/queue control listMessages
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-3141
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3141
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The list methods of queue control that are exposed via jmx seem to be
> unbounded.
> 1) they list all messages
> 2) they display the full body
> To protect both the broker and the browser/UI/client it would make sense to
> limit both the number of messages and the size of the data that is returned.
> Imaging 500k messages pending messages with a body of 10k... and 400k are
> paged to disk. It would be crazy to try and list those.
> I need to do some more tests to verify the extent a broker will do to support
> the current api. I note that the browse functionality can be paged and with
> out a page defaults to 200 messages. That is sensible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
