[
https://issues.apache.org/jira/browse/AMQ-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-9654:
--------------------------------
Description:
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.
was:
Environment:
Linux OS
ActiveMQ 5.17.6
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.
> Queue size incorrect when queue is empty
> ----------------------------------------
>
> Key: AMQ-9654
> URL: https://issues.apache.org/jira/browse/AMQ-9654
> Project: ActiveMQ Classic
> Issue Type: Bug
> Reporter: Matt Pavlovich
> Priority: Major
>
> 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
