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 2019/08/28 19:54:00 UTC
[jira] [Resolved] (ARTEMIS-2463) Message Acknowledge Resets to 0
Whenever the JMS Listener is stop/restarted
[ https://issues.apache.org/jira/browse/ARTEMIS-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-2463.
-------------------------------------
Resolution: Not A Problem
> Message Acknowledge Resets to 0 Whenever the JMS Listener is stop/restarted
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-2463
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2463
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Fem
> Priority: Major
> Attachments: Screenshot 2019-08-28 at 11.02.29 am.png, Screenshot 2019-08-28 at 11.03.33 am.png, Screenshot 2019-08-28 at 11.03.46 am.png, Screenshot 2019-08-28 at 11.04.38 am.png
>
>
> Hi, regarding the *dequeued count on ActiveMQ*, based on my understanding, the counterpart metric of dequeued count in Artemis is *Message acknowledge* so I was doing an experiment on the consuming of message on Artemis and whether the message acknowledges moves as per the consume messages. I created a JMS Listener on a Java application and the queue is successfully shown the changes on the metric *MessagesAcknowledged* , but whenever the JMS Listener is stopped, the metric resets the value to 0 and had no idea where the value goes. So I tried to do the consuming and producing using the default feature on Artemis as per attached files. And yet I am receiving the same output.
> So I guess its either my metric is incorrect or that Artemis does not save or process where the dequeued messages are. Please help (flag) thanks a lot
>
> P.S I did this on two versions: 2.7 and 2.9
--
This message was sent by Atlassian Jira
(v8.3.2#803003)