[
https://issues.apache.org/jira/browse/AMQ-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039684#comment-18039684
]
Matt Pavlovich commented on AMQ-9654:
-------------------------------------
Possible source of issue: TransactionBroker, which modifies message count based
on transaction size (aka opCount)
> Queue size incorrect even when queue is empty
> ---------------------------------------------
>
> Key: AMQ-9654
> URL: https://issues.apache.org/jira/browse/AMQ-9654
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.17.6
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Time Spent: 20m
> 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
