[
https://issues.apache.org/jira/browse/AMQ-9654?focusedWorklogId=972412&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-972412
]
ASF GitHub Bot logged work on AMQ-9654:
---------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jun/25 14:46
Start Date: 10/Jun/25 14:46
Worklog Time Spent: 10m
Work Description: mattrpav opened a new pull request, #1454:
URL: https://github.com/apache/activemq/pull/1454
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 972412)
Remaining Estimate: 0h
Time Spent: 10m
> Queue size incorrect even when queue is empty
> ---------------------------------------------
>
> Key: AMQ-9654
> URL: https://issues.apache.org/jira/browse/AMQ-9654
> Project: ActiveMQ Classic
> Issue Type: Bug
> Affects Versions: 5.17.6
> Reporter: Matt Pavlovich
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Environment:
> Linux OS
> ActiveMQ 5.17.6 using network of brokers (2-3 brokers per cluster)
> Cloud deployment with high frequency of network inconsistency
> 1. Queue size may reflect a small number of messages are still pending on the
> queue (1 or 2), but there are no messages present.
> 2. Broker restart corrects the messages
> 3. No clear indications of exception or error in broker or client-side logs
> 4. Application consuming messages using multiple consumers and
> single-message-per-transaction using local transaction ack mode. (Camel JMS,
> Spring, etc)
> 5. Across dozens of brokers processing 100's of millions of messages per
> year, this will occur a handful of times in all.
> Suspect queue size counter consistency issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
