[
https://issues.apache.org/jira/browse/ARTEMIS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361794#comment-17361794
]
Erwin Dondorp commented on ARTEMIS-3342:
----------------------------------------
tested with apache-artemis-2.18.0-20210611.113905-158-bin.tar.gz
CORE --> messages stored on disk, and marked as "large" in GUI --> OK
AMQP --> messages stored on disk, and not marked as "large" in GUI --> FAIL
But I totally goofed on my conclusion that the files were not removed on
message expiration. As the messages were moved to an ExpiryQueue, the files
remain in use until they expire from there as well (or are deleted). So, back
to the original title/description. Also reduced the priority again. Still
keeping the priority as "high" as the system's performance is greatly reduced
to below our minimum when large messages are used, and this situation should be
clearly visible.
> large AMQP messages are not shown as such in GUI
> ------------------------------------------------
>
> Key: ARTEMIS-3342
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3342
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
> Attachments: image-2021-06-11-14-40-13-673.png,
> image-2021-06-11-14-40-44-094.png
>
>
> When using "large" AMQP messages, the large message are stored properly on
> disk.
> But the the messages are not flagged as "large" message.
> (btw, CORE messages are properly marked as "large")
> see the following screen images:
> I highlighted the message-ID to show that it is properly stored in the
> "large-messages" directory.
> The "largeMessage" field above it still shows "false"
> !image-2021-06-11-14-40-13-673.png!
>
> And on disk:
> !image-2021-06-11-14-40-44-094.png!
>
> Note that this was a durable message. the same effect is present for
> non-durable messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
