[ARTEMIS-3128] Queue browser may cause OutOfMemoryError on server side

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.15.0
• Fix Version/s: 2.18.0
• Component/s: JMX, Web Console

Environment

Embedded Apache Artemis 2.15.0

Windows Server 2016 Standard (10.0.14393)

Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

• Assignee: Gary Tully
• Reporter: Christian Danner
• Created: 19/Feb/21 17:14
• Updated: 18/Oct/21 20:00
• Resolved: 26/Mar/21 14:43

Description

It seems the browse message view in the web console is implemented in a way that the server loads all messages to display per page into memory.

This may lead to an OutOfMemoryError on server side in case many large messages are enqueued.

We use Apache Artemis to transmit large binary messages using AMQP (message sizes of up to 60MB). Producing and consuming messages works just fine as we disable prefetch for consumers, however browsing messages is basically not possible in such a scenario.

Since the queue browser displays basic message properties only it should not be necessary to actually load messages from the journal into memory just to display those message properties.

Only in case the user wants to view message details the client should issue a call to the server to get the actual message payload, preferably with a (configurable) size cap to avoid transmission of large amounts of unnecessary data (viewing binary payloads is of limited use anyways, however a cap also makes sense for text messages)

Issue Links

• is fixed by: ARTEMIS-3141 limit the amount of data returned from jmx/queue control listMessages
• is fixed by: ARTEMIS-3175 Restrict/truncate messages attributes to a configurable limit for management views
• is related to: ARTEMIS-3531 adding documentation for management-message-attribute-size-limit