[
https://issues.apache.org/jira/browse/ARTEMIS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Roskvist updated ARTEMIS-3646:
------------------------------------
Description:
{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}
was:
{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:
# java -jar shaded-jars/AmqJmsProducer.jar -url "tcp://localhost:61616" -user
USER -pw PASSWORD -queue TEST -count 100
# java -jar shaded-jars/AmqJmsConsumer.jar -url "tcp://localhost:61616" -user
USER -pw PASSWORD -queue TEST -count 1 -rollback 100 -t 10
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}
> 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
>
> {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)
