[
https://issues.apache.org/jira/browse/ARTEMIS-4952?focusedWorklogId=927476&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-927476
]
ASF GitHub Bot logged work on ARTEMIS-4952:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/24 23:51
Start Date: 25/Jul/24 23:51
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #5117:
URL: https://github.com/apache/activemq-artemis/pull/5117
Issue Time Tracking
-------------------
Worklog Id: (was: 927476)
Time Spent: 0.5h (was: 20m)
> JMX countMessages: groupBy not working on AMQP messages
> -------------------------------------------------------
>
> Key: ARTEMIS-4952
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4952
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMX, management
> Affects Versions: 2.35.0
> Reporter: nmeylan
> Priority: Minor
> Attachments: image-2024-07-25-09-54-32-066.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I encountered weird behavior with JMX _countMessages(String, String)_ when
> messages are produced via *AMQP* then moved to another queue and when I call
> *countMessages* operation with a group by
> h2. Context:
> * I create *1600 *messages to *queue.1*, using *CORE* protocol
> * I create *440 *messages to *queue.2*, using *AMQP* protocol
> * I move all messages from *queue.1* to *dl.default* queue, using
> moveMessages operation
> * I move all messages from *queue.2* to *dl.default* queue, using
> moveMessages operation
>
> h2. Current behavior
> Calling *countMessages* operation on queue *dl.default* with a groupBy _
> _AMQ_ORIG_QUEUE_ i get:
> {code}
> {"null": 440, "queue.1": 1600}
> {code}
> If I also filter by _ _AMQ_ORIG_QUEUE='queue.2'_ i get
> {code}
> {"null": 440}
> {code}
> !image-2024-07-25-09-54-32-066.png!
>
> h2. Expected behavior
> Calling *countMessages* operation on queue *dl.default* with a groupBy _
> _AMQ_ORIG_QUEUE_ i get:
> {code}
> {"queue.2": 440, "queue.1": 1600}
> {code}
> h2. Notes
> I was wondering why
> [message.getObjectProperty|https://github.com/apache/activemq-artemis/blob/41ec279e2240fd4a84e1c0e7902623682bc5e785/artemis-server/src/main/java/org/apache/activemq/artemis/core/management/impl/QueueControlImpl.java#L1164]
> is called instead of
> [message.getObjectPropertyForFilter|https://github.com/apache/activemq-artemis/blob/41ec279e2240fd4a84e1c0e7902623682bc5e785/artemis-server/src/main/java/org/apache/activemq/artemis/core/filter/impl/FilterImpl.java#L237]
> as for filtering
> I did the test using getObjectPropertyForFilter instead of getObjectProperty
> and it works
--
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
