You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/08/09 14:55:00 UTC
[jira] [Commented] (ARTEMIS-3416) Message count is not zero even
after all messages are consumed and acknowledged
[ https://issues.apache.org/jira/browse/ARTEMIS-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396085#comment-17396085 ]
Justin Bertram commented on ARTEMIS-3416:
-----------------------------------------
Messages which are "in delivery" are those which have been dispatched to a client but not yet acknowledged. They are not available to be browsed. Therefore, the screenshots of the broker you provided are consistent with the expected behavior.
The broker clearly believes there is still 1 message which has not yet been acknowledged. However, given your description it appears that your application should be acknowledging every message. Could there possibly be a bug in your application where it is not, in fact, acknowledging every message? If you don't believe there is a bug in your application can you provide a test-case which reproduces this issue or at least provide [DEBUG|https://activemq.apache.org/components/artemis/documentation/latest/logging.html#activating-trace-for-a-specific-logger] logs [for STOMP|https://activemq.apache.org/components/artemis/documentation/latest/stomp.html#logging] along with the output from the {{listDeliveringMessagesAsJSON}} management method?
> Message count is not zero even after all messages are consumed and acknowledged
> -------------------------------------------------------------------------------
>
> Key: ARTEMIS-3416
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3416
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.16.0
> Environment: Single artemis instance running as a K8s deployment with single replica on CentOS 7.9
> Reporter: Amit Herlekar
> Priority: Minor
> Attachments: image-2021-08-06-17-19-37-446.png, image-2021-08-06-17-20-45-445.png, image-2021-08-06-17-24-45-732.png
>
>
> 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|https://keda.sh/docs/2.4/scalers/artemis/].
> 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.
> !image-2021-08-06-17-24-45-732.png|width=638,height=571!
> !image-2021-08-06-17-19-37-446.png|width=811,height=674!
> !image-2021-08-06-17-20-45-445.png|width=671,height=300!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)