Having the amqsrua sample print a little blurb in its output about this behavior would go a long way to clear up the confusion.
Original Message:
Sent: Fri October 11, 2024 07:29 AM
From: Peter Roemer
Subject: amqsrua
Hi Andrew,
thanks for your explanation. Now I understand the interval of 5 days.
The queuemanager was indeed restarted 5 days ago.
Kindly regards,
Peter
------------------------------
Peter Roemer
Original Message:
Sent: Fri October 11, 2024 06:35 AM
From: Andrew Hickson
Subject: amqsrua
Amqsruaa is an MQ sample, it subscribes to MQ system topics and reports the published statistics.
This stats mechanism is optimized so that stats are only published when there is one or more subscriber subscribed to the topics of relevance.
As long as at least one subscriber to stats for a specific queue is available the queue manager will report the stats interval since the last publication for that queue. When the last subscriber to the system topic of interest unsubscribes then the queue manager stops publishing to this particular (queue specific) topic and the next new subscriber to system stats for this specific queue will be sent the stats for the time since the queue manager started.
None of this is particularly elegant, but it is/was cheap to implement and also avoids the overhead of collecting and reporting the stats becoming intrusive.
------------------------------
Andrew Hickson
Original Message:
Sent: Fri October 11, 2024 04:15 AM
From: Peter Roemer
Subject: amqsrua
Hi Francois,
"The 4 days, 16 hours, 2 minutes and x many seconds is the first snapshot. it shows the interval to the preceding snapshot as this is not 10 seconds."
This was my first snapshot, or, the first time I run amqsrua on the queuemanager QM_PRD.
That's why it's not clear to me what the first snapshot means;
I just run the amqsrua on the same object again and the intterval now is:
Interval: 5 days, 11 hours, 5 minutes....
Interval has increased by 1 day
Kindly regards,
Peter
------------------------------
Peter Roemer
Original Message:
Sent: Fri October 11, 2024 01:23 AM
From: Francois Brandelik
Subject: amqsrua
Hi Peter,
If you remove the -n 2 parameter, you will see that the tool takes a snapshot every 10 seconds.
The 4 days, 16 hours, 2 minutes and x many seconds is the first snapshot. it shows the interval to the preceding snapshot as this is not 10 seconds.
What is interresting is that in the last 10 seconds the tool ran you have an MQGET rate of 2 msgs per second for persistent messages and at the same time a failed MQGET rate of 2 msgs per second with no particular reason for the fail...
Were the 23 messages rolled back?
Hope this helps.
------------------------------
Francois Brandelik
Original Message:
Sent: Thu October 10, 2024 08:21 AM
From: Peter Roemer
Subject: amqsrua
Hi,
I run the Monitoring system resource usage by amqsrua. See output below.
The first view shows an interval of 4 days, 16 hours,etc... The second view shows an interval of 10.000 seconds.
What means the interval of 4 days, 16 hours, etc ? What was 4 days ago ? restart of the application (not the queuemanager) ?
/opt/mqm/samp/bin/amqsrua -m QM_PRD -c STATQ -t GET -o DIG.CUST_ORDER_RESPONSE.DAT -n 2
Publication received PutDate:20241010 PutTime:12114143 Interval:4 days,16 hours,2 minutes,3.747 seconds
DIG.CUST_ORDER_RESPONSE.DAT MQGET count 53345
DIG.CUST_ORDER_RESPONSE.DAT MQGET byte count 1700964759 4217/sec
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET non-persistent message count 1
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET persistent message count 53344
DIG.CUST_ORDER_RESPONSE.DAT rolled back MQGET count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET non-persistent byte count 53793
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET persistent byte count 1700910966 4217/sec
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse non-persistent message count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse persistent message count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse non-persistent byte count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse persistent byte count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails 53365
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails with MQRC_NO_MSG_AVAILABLE 10
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails with MQRC_TRUNCATED_MSG_FAILED 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails with MQRC_NO_MSG_AVAILABLE 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails with MQRC_TRUNCATED_MSG_FAILED 0
Publication received PutDate:20241010 PutTime:12115143 Interval:10.000 seconds
DIG.CUST_ORDER_RESPONSE.DAT MQGET count 23 2/sec
DIG.CUST_ORDER_RESPONSE.DAT MQGET byte count 1053624 105360/sec
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET non-persistent message count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET persistent message count 23 2/sec
DIG.CUST_ORDER_RESPONSE.DAT rolled back MQGET count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET non-persistent byte count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET persistent byte count 1053624 105360/sec
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse non-persistent message count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse persistent message count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse non-persistent byte count 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse persistent byte count 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails 23 2/sec
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails with MQRC_NO_MSG_AVAILABLE 0
DIG.CUST_ORDER_RESPONSE.DAT destructive MQGET fails with MQRC_TRUNCATED_MSG_FAILED 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails with MQRC_NO_MSG_AVAILABLE 0
DIG.CUST_ORDER_RESPONSE.DAT MQGET browse fails with MQRC_TRUNCATED_MSG_FAILED 0
Regards,
Peter
------------------------------
Peter Roemer
------------------------------