You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/01 12:43:00 UTC

[jira] [Work logged] (ARTEMIS-3646) OpenWire clients leave incorrect queue metrics when messages are sent to DLQ

     [ https://issues.apache.org/jira/browse/ARTEMIS-3646?focusedWorklogId=718639&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-718639 ]

ASF GitHub Bot logged work on ARTEMIS-3646:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Feb/22 12:42
            Start Date: 01/Feb/22 12:42
    Worklog Time Spent: 10m 
      Work Description: AntonRoskvist opened a new pull request #3936:
URL: https://github.com/apache/activemq-artemis/pull/3936


   …cs for messages sent to DLQ


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 718639)
    Remaining Estimate: 0h
            Time Spent: 10m

> OpenWire clients leave incorrect queue metrics when messages are sent to DLQ
> ----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3646
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3646
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Anton Roskvist
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {color:#1d1c1d}Messages getting sent to DLQ from an OpenWire client leaves incorrect queue metrics behind. {color}{color:#1d1c1d}"DeliveringSize"
> "DurableDeliveringSize" 
> "DurablePersistentSize"
> "PersistentSize"
> All metrics above end up with negative values, even if the consumers are later disconnected or if the messages are retried and successfully consumed.
> I am able to reproduce this easily with an Artemis broker running "out-of-the-box"-config and using the following clients:
> [https://github.com/erik-wramner/JmsTools]   (AmqJmsConsumer.jar and AmqJmsProducer.jar)
> Example: 
> {color}
> {code:java}
> # java -jar shaded-jars/AmqJmsProducer.jar -url "tcp://localhost:61616" -user USER -pw PASSWORD -queue TEST -count 100{code}
> {code:java}
> # java -jar shaded-jars/AmqJmsConsumer.jar -url "tcp://localhost:61616" -user USER -pw PASSWORD -queue TEST -count 1 -rollback 100 -t 10{code}
> {color:#1d1c1d}
> Using Artemis clients from the same tools results in no such issue. I am seeing the issue with other OpenWire clients also
> Br,{color}
> {color:#1d1c1d}Anton{color}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)