Thanks for following up, Fredrik.
I believe the changes from ARTEMIS-4065 [1] will resolve your issue in
2.28.0. You can test your reproducer with a snapshot [2] in the mean-time
if you like.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4065
[2]
In Justin Bertram wrote:
> I see you're using a metrics plugin. Is this what you're using to
> determine the message count?
Indeed. Though I believe I have confirmed that artemis post office api
report the same value as the micrometer metrics plugin. See test case below.
My current hunch is
I see you're using a metrics plugin. Is this what you're using to determine
the message count? If so, do you have any other way to determine the
message count (e.g. directly from the queue's MBean) in your embedded
environment? I'm asking because I want to eliminate the possibility that
something
Hi,
Justin, thanks for your advice. I must say, the help given in Apache
communities and on mailinglists are awesome. Cheers everyone! :)
The reasons I believe the count is wrong are: For the period of a few weeks
now, I have performed a handfull of orderly shutdowns and starts of the
embedded
> Is there anything I can do to encourage Artemis to perform a "recount" of
the messages that actually are persisted in the queues?
The broker should recount the messages every time it starts and loads the
journal from disk. You could use the `artemis data print` command to take a
close look at
Hi,
I have an embedded Artemis 2.27.1 broker with jvm local connections in a
spring boot app. I believe that the metrics for artemis_message_count of
two queues are wrong. They never go below a certain base threshold, in one
case 146, in the other 86. Not much, but annoying nontheless.
The
.n4.nabble.com/Strange-problem-in-activeMQ-or-Camel-resulting-in-wrong-message-type-tp4673120.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Tue, 2010-03-30 at 12:31 -0400, Gabe Westmaas wrote:
Below is a slightly edited version of a tcp dump on the activemq side of a
transaction between an NMS 1.2 client and ActiveMQ 5.3.
MESSAGE
message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:-1:1:14
BEGIN
