Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.16.0
-
None
-
None
-
None
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.
- moveMessages(String, String)
- 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.
Attachments
Attachments
Issue Links
- is caused by
-
ARTEMIS-3021 OOM due to wrong CORE clustered message memory estimation
- Closed
- Testing discovered
-
ARTEMIS-3575 Wrong address size estimation on broker restart
- Closed
-
ARTEMIS-3578 Save SimpleString duplication and long[] allocation while moving Core messages
- Closed