[jira] [Work logged] (ARTEMIS-3141) limit the amount of data returned from jmx/queue control listMessages

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3141?focusedWorklogId=563720&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-563720 ]

ASF GitHub Bot logged work on ARTEMIS-3141:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Mar/21 13:16
            Start Date: 10/Mar/21 13:16
    Worklog Time Spent: 10m 
      Work Description: gtully opened a new pull request #3484:
URL: https://github.com/apache/activemq-artemis/pull/3484


   …x operations that use a queue browser


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 563720)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  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 imagine a:
>  management-list-messages-max default 256
>  management-list-messages-body-max default 256 or some such.
> 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)