| Author |
Message
|
| ibmmqrock |
 Posted: Tue Aug 13, 2019 3:13 pm Post subject: How to found out if some messages has expired |
 |
|
Novice
Joined: 30 May 2019
Posts: 14
|
Our Performance testing team are running load test and they have mentioned that they are not receiving responses after running performance test after some time.
I am wondering if response message is getting expired, we have set CAPEXPRY on the Queue to 1 minute.
Is there a way in MQ to know how many messages (if any) got expired in this queue at a specific interval. We don't want to run tracing as it generates too many log files.
Please suggest if there is any way to find that out. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Aug 13, 2019 3:36 pm Post subject: Re: How to found out if some messages has expired |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| ibmmqrock wrote: |
Our Performance testing team are running load test and they have mentioned that they are not receiving responses after running performance test after some time.
I am wondering if response message is getting expired, we have set CAPEXPRY on the Queue to 1 minute.
Is there a way in MQ to know how many messages (if any) got expired in this queue at a specific interval. We don't want to run tracing as it generates too many log files.
Please suggest if there is any way to find that out. |
Expiry value of the MQMD is set for each message by applications at MQPUT, and represents time-to-live - after which the message will not be delivered to any consuming application. MQ's internal garbage collection process will delete expired messages from queues.
CAEXPRY sets the maximum expiry value allowed for a queue or topic.
What Expiry value does the application specify?
The application can specify ReportOptions at MQPUT time that will create a ReportMessage when/if messages expire. These ReportMessages will be delivered to the ReplyToQueue; and the app will need to process these messages, and take appropriate action. Visit this site: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q097680_.htm . Look at MQRO_EXPIRATION.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| markt |
| Posted: Tue Aug 13, 2019 11:14 pm Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| Code: |
| amqsrua -m <qmgr> -c STATQ -t GET -o <qname> |
will show expiry count for a particular queue as they happen.
As will qmgr statistics records if they are enabled. Use amqsmon to generate those reports. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 14, 2019 4:33 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| bobbee |
| Posted: Wed Sep 14, 2022 4:20 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
amqsrua -m <qmgr> -c STATQ -t GET -o <qname>
Is this the only way to get to this number?
When is this count reset? |
|
| Back to top |
|
|
| Andyh |
| Posted: Thu Sep 15, 2022 12:40 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
The counters used by amqsrua are independant of those used by the MQ stats mechanism.
amqsrua is a sample program (as are all amqs prefixed programs) and as such the source code is shipped with the product and can be used as a starting point for your own monitoring programs.
amqsrua subscribes to the appropriate system topics to obtain the information to be reported. The queue manager publishes this information based upon internal monatonically increasing counters (as such, never reset). The same counters can be found in raw form in appropriate FDC's or in the data published by the amqldmpa service program. |
|
| Back to top |
|
|
|
|
