Why there is no monitoring topic for queue destroy event?
Article ID: KB0086935
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
The reason we don't provide a queue destroy monitor event is that queue destroy occurs in batches.
This would cause a burst of event monitors that could possibly slow the server down, causing latency spikes, etc.
Depending on what you want to achieve, periodically using the .NET admin API ServerInfo.QueueCount() method may help.
If you want to measure the deltas (created and destroyed), could subscribe to "queue create" events, use the admin API to get the initial set, and then periodically query individual queues for information. If an individual queue doesn't exist, they will remove it from their set, and get the “deltas” of created and destroyed.
The reason we don't provide a queue destroy monitor event is that queue destroy occurs in batches.
This would cause a burst of event monitors that could possibly slow the server down, causing latency spikes, etc.
Depending on what you want to achieve, periodically using the .NET admin API ServerInfo.QueueCount() method may help.
If you want to measure the deltas (created and destroyed), could subscribe to "queue create" events, use the admin API to get the initial set, and then periodically query individual queues for information. If an individual queue doesn't exist, they will remove it from their set, and get the “deltas” of created and destroyed.
Issue/Introduction
Why there is no monitoring topic for queue destroy event?
Feedback
Yes
No
Powered by
