You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2023/10/27 22:19:00 UTC

[jira] [Commented] (ARTEMIS-4469) Setting the _AMQ_LARGE_COMPRESSED header when sending a compressed message

    [ https://issues.apache.org/jira/browse/ARTEMIS-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780550#comment-17780550 ] 

Justin Bertram commented on ARTEMIS-4469:
-----------------------------------------

bq. If a client mistakenly sets _AMQ_LARGE_COMPRESSED...

Are you talking about the core or core JMS client mistakenly setting the {{_AMQ_LARGE_COMPRESSED}} property or are you talking about a messaging application mistakenly setting it? If the former, do you have a use-case where it's being mistakenly set? If the latter, this is just a bug in the messaging application since the {{_AMQ_LARGE_COMPRESSED}} property is an internal property and shouldn't be used by a messaging application.

> Setting the _AMQ_LARGE_COMPRESSED header when sending a compressed message
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4469
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4469
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.30.0
>            Reporter: Kirill Chadakin
>            Priority: Major
>
> When compressing the message body, the final size may be smaller than the threshold value for the body size at which the message is considered large (min-large-message-size). When sending a large message, the _AMQ_LARGE_COMPRESSED header is set to true if the message is compressed, and false if it is uncompressed. When sending a regular message, the header is not set. If a client mistakenly sets _AMQ_LARGE_COMPRESSED to true when sending a regular message, an error will occur during the message unpacking process when receiving such a message from the queue. This can be fixed by forcibly setting the _AMQ_LARGE_COMPRESSED header for both large and regular messages.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)