[ARTEMIS-3141] limit the amount of data returned from jmx/queue control listMessages

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.0
• Fix Version/s: 2.18.0
• Component/s: JMX
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 24/Feb/21 11:43
• Updated: 20/Oct/21 10:40
• Resolved: 10/Mar/21 16:16

Description

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.

Issue Links

• fixes: ARTEMIS-3128 Queue browser may cause OutOfMemoryError on server side
• incorporates: ARTEMIS-3175 Restrict/truncate messages attributes to a configurable limit for management views
• is related to: ARTEMIS-3492 Not able to view full payload in artemis 2.18 console
• is related to: ARTEMIS-3531 adding documentation for management-message-attribute-size-limit
• links to: GitHub Pull Request #3484