Address Memory Used increases by 60% when messages are moved to another queue

Solution Verified - Updated -

Issue

When messages moved from one durable queue to another durable queue by performing moveMessages(String, String) operation, there is change in address memory. It increases approximately by 60%. The same thing noticed when the broker moves messages from a queue to the DLQ.

Steps to reproduce the issue :-
• 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

Environment

  • Red Hat AMQ
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content