[ARTEMIS-3416] Message count is not zero even after all messages are consumed and acknowledged

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 2.16.0
• Component/s: Broker

Environment

Single artemis instance running as a K8s deployment with single replica on CentOS 7.9

• Flags: Important
• Assignee: Unassigned
• Reporter: Amit Herlekar
• Created: 06/Aug/21 11:58
• Updated: 14/Aug/21 14:07
• Resolved: 14/Aug/21 14:07

Description

We have switched from ActiveMQ Classic to ActiveMQ Artemis. Thanks to the nice documentation on github that we are able to containerize it and deploy it as a K8s deployment for KEDA.

Coming to the issue, we are using STOMP using stomp.py python module. The ACK-mode is set as client-individual and consumerWindowSize = 0 on the connection. We are promptly acknowledging the message as soon as we read it. 

The problem is, sometimes, the message count in the web console does not become zero even after all the messages are actually consumed and acknowledged. When I browse the queue, I don't see any messages in it. This is causing KEDA to spin up pods unnecessarily. 

Please refer to the screenshots attached. 

As a temporary arrangement, can you let me now how to make the delivery message count = 0.