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

Erwin Dondorp commented on ARTEMIS-4781:
----------------------------------------

[~jbertram] 

I was able to simplify the scenario and to add a reproducer.

> on-disk files for large messages are not always removed
> -------------------------------------------------------
>
>                 Key: ARTEMIS-4781
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4781
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 2.33.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>         Attachments: Test4781LargeMsgOnDisk.java, reproducer-output.txt
>
>
> SETUP:
> Using a broker-cluster.
> We are producing big AMQP messages on the first node and consume them from 
> the second node.
> The size of the messages is chosen so that these are around the 
> min-large-message-size.
> OBSERVATION:
> For specific message sizes, the TMP files on the second node are not removed 
> even when the message is consumed.
> My assumption is that this occurs for those messages that are not initially 
> LARGE messsages, but which become LARGE messages due to the movement of the 
> messages between the cluster nodes. During this process a few administrative 
> (or informative?) message headers are added by the broker causing the message 
> size to be increased so that it is now a large message.
> REPRODUCER
> The reproducer sets-up a cluster of 2 nodes and leaves the 
> min-large-message-size at the default 102400 bytes.
> The reproducer sends text-messages with a text-payload between 90KiB and 
> 110KiB, increasing each time with 50 bytes. this results in a range of just 
> over 400 messages.
> In this scenario, 7 files are left in the large-msgs directory after test is 
> completed and all software is ended. The files have file-sizes 102433 through 
> 102733 bytes.
> There were no functional problems, all messages were properly produced and 
> consumed.
> REPRODUCER INSTRUCTIONS
> place attached file in directory 
> {{[activemq-artemis]/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/amqp}}
> run with: {{cd tests/integration-tests && mvn 
> -Dmaven.test.redirectTestOutputToFile=false -DskipIntegrationTests=false 
> -Dtest="Test4781LargeMsgOnDisk" clean test}}
> the output of the reproducer is also attached.
> NOTE:
> the title+description of this issue has been updated significantly as 
> initially a much more complicated scenario was described. further 
> investigation has shown that it was actually a simpler scenario.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact


Reply via email to