Is it possible to configure TIBCO Enterprise Message Service (EMS) to bridge system monitoring topics "$sys.monitor.q.*." to a queue to persist them for recovery on failure?
Article ID: KB0089627
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
=========
TIBCO EMS server cannot be configured to bridge system monitoring topics "$sys.monitor.q.*.>" messages to a queue. The bridge works only for incoming messages (imported from RV or incoming EMS messages). Monitor messages are generated by the EMS Server and therefore can not be bridged.
The Monitor messages are RELIABLE messages, not PERSISTENT messages, so they are not supposed to be recovered after an EMS restart, even if there was a durable subscriber on a monitor topic. There is no way for subscribing client programs for monitoring messages to receive all messages in the event of an EMS failure.
The only way to accomplish this is to have a client consuming the monitor messages and persisting them, but this does not happening automatically because, as stated above, monitor messages are reliable, not persistent. This also means that you would need to have a consumer running at all times for monitor messages.
In the past an enhancement request (#1-7ADX03) was created to for EMS Monitor messages to be persisted to prevent their loss if a server went down. The enhancement request was rejected by the ER review board as the monitor message are meant to be informational only. Persisting these messages would have had a huge impact on EMS server performance.
Environment:
==========
All EMS versions and Operating Systems.
Description:
=========
TIBCO EMS server cannot be configured to bridge system monitoring topics "$sys.monitor.q.*.>" messages to a queue. The bridge works only for incoming messages (imported from RV or incoming EMS messages). Monitor messages are generated by the EMS Server and therefore can not be bridged.
The Monitor messages are RELIABLE messages, not PERSISTENT messages, so they are not supposed to be recovered after an EMS restart, even if there was a durable subscriber on a monitor topic. There is no way for subscribing client programs for monitoring messages to receive all messages in the event of an EMS failure.
The only way to accomplish this is to have a client consuming the monitor messages and persisting them, but this does not happening automatically because, as stated above, monitor messages are reliable, not persistent. This also means that you would need to have a consumer running at all times for monitor messages.
In the past an enhancement request (#1-7ADX03) was created to for EMS Monitor messages to be persisted to prevent their loss if a server went down. The enhancement request was rejected by the ER review board as the monitor message are meant to be informational only. Persisting these messages would have had a huge impact on EMS server performance.
Environment:
==========
All EMS versions and Operating Systems.
Issue/Introduction
Is it possible to configure TIBCO Enterprise Message Service (EMS) to bridge system monitoring topics "$sys.monitor.q.*." to a queue to persist them for recovery on failure?
Feedback
Yes
No
Powered by
