[jira] [Closed] (ARTEMIS-3614) Setting minLargeMessageSize in the broker.xml acceptor doesn't do anything

["Kyle S (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kyle S closed ARTEMIS-3614.
---------------------------
    Resolution: Not A Bug

Wasn't a bug

> Setting minLargeMessageSize in the broker.xml acceptor doesn't do anything
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3614
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3614
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.19.0
>         Environment: OS: Windows Server 2022 Datacenter Azure Edition
> Processor    Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz   2.10 GHz
> Installed RAM    8.00 GB
> System type    64-bit operating system, x64-based processor
>            Reporter: Kyle S
>            Priority: Major
>         Attachments: explorer_2021-12-17_14-12-29.png, msedge_2021-12-17_14-07-44.png
>
>
> I currently trying to send a file to ActiveMQ Artemis that's 174 KB (178,194 bytes) as reported by Windows. I'm sending this file over TCP using the openwire protocol.
> My acceptor is configured as follows:
>  
> {noformat}
> <acceptor name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;minLargeMessageSize=102400;protocols=CORE,AMQP,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false</acceptor>{noformat}
>  
> When I send the file, the persistent size is 349.10 KB which is close enough to expectations since ActiveMQ artemis stores each character as 2 bytes, essentially doubling the size of what I'm sending.
>  
> The problem is, I have minLargeMessage size set to 102,400 bytes so that means that my file of 178,194 bytes should be flagged as large, but it's not. Setting minLargeMessageSize to -1 also seems to have no effect.
> My goal is to actually increase this limit so that I can view messages in the queue as needed for troubleshooting, but this URL parameter doesn't seem to be used.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)