[ARTEMIS-3572] Address Memory Used increases by 60% when messages are moved to another queue

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.16.0
• Assignee: Unassigned
• Reporter: Daniel Claesén
• Created: 15/Nov/21 09:27
• Updated: 16/Nov/21 10:04

Description

When I manually move messages from one durable queue to another the address memory used increases by 60%. I expect the address memory used to remain the same as before the messages were moved.

The same thing happens when the broker moves messages automatically from a queue to the DLQ.

Steps to reproduce:

• Using the GUI in the console:
  • Create a new multicast address named "mytest"
  • Select the address and create a durable multicast queue named "mytest"
• Use the artemis CLI to produce messages. For example like this:
  • artemis producer --user admin --password admin --url tcp://localhost:61616 --destination topic://mytest --message-count 1000 --message-size 40960 --threads 4
• Note the reported address memory used in the console
  • In the example above it is 160.26MB
• Use the GUI in the console to move messages. For example with the following operation:
  • moveMessages(String, String)
    • Keep the filter param empty and enter "DLQ" in the otherQueueName param.
• The reported address memory used in the console is now 60% higher
  • In my example the reported size was 256.43MB

 

I have a Red Hat ticket (https://access.redhat.com/support/cases/#/case/03076511) about this and it was suggested that I should create Jira ticket to discuss it further with developers. It was mentioned that management calls themselves use memory and that this could be causing the issue, but I don't see why management calls would use address memory.

Issue Links

• is caused by: ARTEMIS-3021 OOM due to wrong CORE clustered message memory estimation
• Testing discovered: ARTEMIS-3575 Wrong address size estimation on broker restart
• Testing discovered: ARTEMIS-3578 Save SimpleString duplication and long[] allocation while moving Core messages