You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2025/11/20 18:04:00 UTC
[jira] [Commented] (AMQ-9654) Queue size incorrect even when queue is empty
[ https://issues.apache.org/jira/browse/AMQ-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039677#comment-18039677 ]
Matt Pavlovich commented on AMQ-9654:
-------------------------------------
Add'l log message from recent Apache CI run:
{noformat}
[ERROR] Tests run: 22, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 19.68 s <<< FAILURE! -- in org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest
[ERROR] org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario[sendDupToDLQ=false,cacheEnable=true,auditEnabled=true,optimizedDispatch=true] -- Time elapsed: 0.608 s <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.doProcessSendDuplicateFromStoreToDLQ(SendDuplicateFromStoreToDLQTest.java:172)
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario(SendDuplicateFromStoreToDLQTest.java:134)
[ERROR] org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario[sendDupToDLQ=false,cacheEnable=true,auditEnabled=false,optimizedDispatch=false] -- Time elapsed: 0.528 s <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.doProcessSendDuplicateFromStoreToDLQ(SendDuplicateFromStoreToDLQTest.java:172)
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario(SendDuplicateFromStoreToDLQTest.java:134)
[ERROR] org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario[sendDupToDLQ=false,cacheEnable=false,auditEnabled=true,optimizedDispatch=true] -- Time elapsed: 0.595 s <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.doProcessSendDuplicateFromStoreToDLQ(SendDuplicateFromStoreToDLQTest.java:172)
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario(SendDuplicateFromStoreToDLQTest.java:134)
[ERROR] org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario[sendDupToDLQ=null,cacheEnable=null,auditEnabled=null,optimizedDispatch=null] -- Time elapsed: 0.561 s <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.doProcessSendDuplicateFromStoreToDLQ(SendDuplicateFromStoreToDLQTest.java:172)
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario(SendDuplicateFromStoreToDLQTest.java:134)
[ERROR] org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario[sendDupToDLQ=false,cacheEnable=true,auditEnabled=false,optimizedDispatch=false] -- Time elapsed: 0.654 s <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.doProcessSendDuplicateFromStoreToDLQ(SendDuplicateFromStoreToDLQTest.java:172)
at org.apache.activemq.broker.policy.SendDuplicateFromStoreToDLQTest.testSendDuplicateFromStoreToDLQScenario(SendDuplicateFromStoreToDLQTest.java:134)
{noformat}
> 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: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact