Why Does the "imqcmd list dst" Command Show Different Numbers of Messages on the Same Destination Depending On Which Clustered Broker it Connects To?
(Doc ID 1300269.1)
Last updated on JUNE 03, 2021
Applies to:Oracle GlassFish Server - Version 7.0 and later
Information in this document applies to any platform.
This article will explain why querying the number of messages using "imqcmd list dst" can show different totals for the same destination, depending on which clustered broker instance the command is run against.
Take, for example, a setup of two Message Queue (MQ) brokers that form an enhanced GlassFish Message Queue broker cluster, where the brokers use a common database store for their messages. In this system there there are MQ clients connected to both or either MQ brokers, producing and consuming messages.
When "imqcmd list dst" is used to query the number of messages for each destination on the brokers, the following output is typical:
Broker 1: <broker1>:<port>:
Notice that both Broker 1 and Broker 2 have different number of messages on one of their queues, Broker 1 reports one message on queue2, while Broker 2 reports two messages on queue2.
- Name shows the name of the topic/queue destination name.
- Wildcard provides the number of wildcard "producer/consumer" this destination has
- "Msgs Count" provides the total message in this BROKER (seen or known).
- "Msgs Remote" provides how many of these messages are non local to this broker.
- "Msgs Unack" means the the number of unacknowledged messages in this destination that have yet to be acknowledged from the client.
- "Msgs Avg Size" provides the average size of the messages processed by this destination.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document