[
https://issues.apache.org/jira/browse/ARTEMIS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361868#comment-17361868
]
Erwin Dondorp commented on ARTEMIS-3342:
----------------------------------------
I recently doubled `amqpMinLargeMessageSize` (and `minLargeMessageSize` for the
CORE acceptor) to 200K, so that 100K character messages would fit; due to the
2-byte internal character encoding.
But the above test was still done with the default value of 100K as it was part
of the "test-before-the-change".
> 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 in the web console.
> (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)
