If messages on a queue expire and do not get sent to the undelivered queue, is there a way to check the number of expired messages?
Article ID: KB0084448
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
==========
With the INFO server tracing option enabled EMS will generate a log message when messages become expired, such as ‘Expired 2 messages’.
To track the messages being expired on a particular destination you can subscribe to the monitor topic $sys.monitor.D.p.<destination_name>, where ‘D’ refers to the type of destination (‘T’ for topic, ‘Q’ for queue), and ‘p’ refers to message expiration events.
Refer to the chapter on ‘Monitor Messages’ and ‘Monitoring Server Activity: Monitoring Server Events’ sections in the EMS User’s Guide for further details.
Environment:
==========
ALL
Description:
==========
With the INFO server tracing option enabled EMS will generate a log message when messages become expired, such as ‘Expired 2 messages’.
To track the messages being expired on a particular destination you can subscribe to the monitor topic $sys.monitor.D.p.<destination_name>, where ‘D’ refers to the type of destination (‘T’ for topic, ‘Q’ for queue), and ‘p’ refers to message expiration events.
Refer to the chapter on ‘Monitor Messages’ and ‘Monitoring Server Activity: Monitoring Server Events’ sections in the EMS User’s Guide for further details.
Environment:
==========
ALL
Issue/Introduction
If messages on a queue expire and do not get sent to the undelivered queue, is there a way to check the number of expired messages?
Feedback
Yes
No
Powered by
