Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.35.0
-
None
Description
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
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
Current behavior
Calling countMessages operation on queue dl.default with a groupBy _ AMQ_ORIG_QUEUE i get:
{"null": 440, "queue.1": 1600}
If I also filter by _ AMQ_ORIG_QUEUE='queue.2' i get
{"null": 440}
Expected behavior
Calling countMessages operation on queue dl.default with a groupBy _ AMQ_ORIG_QUEUE i get:
{"queue.2": 440, "queue.1": 1600}
Notes
I was wondering why message.getObjectProperty is called instead of message.getObjectPropertyForFilter as for filtering
I did the test using getObjectPropertyForFilter instead of getObjectProperty and it works
Attachments
Attachments
Issue Links
- links to