Is there any tool to review the CM Ledger file?
Article ID: KB0087305
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
There is a sample RV C program "tibrvreviewldgr.c" (in <TIB/RV>/src/examples/c directory) which you can use to review the publisher's ledger file.
Unfortunately, other than this, we do not provide any other tool to examine the ledger file.
In RV, the reviewLedger() function call can provide useful information relating to the "real state" of a CM sender's ledger file, if used appropriately. reviewLedger() allows you to query the ledger for stored items related to a subject name, let's say "foo.bar". Therefore, you will be able to retrieve such important information as the following:
===============================================================
Last Sent Message - sequence number of the most recently sent message with subject "foo.bar".
Total Messages - total number of pending messages with subject "foo.bar".
Total Size - total storage (in bytes) occupied by all pending messages with subject "foo.bar".
Last Confirmed - within each listener submessage, the Last Confirmed field contains the sequence number of the last message for which this listener confirmed delivery.
Unacknowledged Messages - number of messages pending for this listenener. The value is computed by subtracting the last sent sequence number from the last acknowledged sequence number.
===============================================================
For details, please refer to tibrvcmTransport_ReviewLedger() in "Chapter 11 Certified Message Delivery" of the RV C API Reference manual (or refer to the chapter "Certified Message Delivery" in eqivalent API reference manual).
Please note that the reviewLedger() calls were intended to be used from within the context of the running CM application; they were not intended to be used by an external application outside of the original runtime context. Hence, the best practice would be to gracefully shut down all relevant pub/sub applications first, then use the reviewLedger() call, by doing so, the results produced should be consistent.
There is a sample RV C program "tibrvreviewldgr.c" (in <TIB/RV>/src/examples/c directory) which you can use to review the publisher's ledger file.
Unfortunately, other than this, we do not provide any other tool to examine the ledger file.
In RV, the reviewLedger() function call can provide useful information relating to the "real state" of a CM sender's ledger file, if used appropriately. reviewLedger() allows you to query the ledger for stored items related to a subject name, let's say "foo.bar". Therefore, you will be able to retrieve such important information as the following:
===============================================================
Last Sent Message - sequence number of the most recently sent message with subject "foo.bar".
Total Messages - total number of pending messages with subject "foo.bar".
Total Size - total storage (in bytes) occupied by all pending messages with subject "foo.bar".
Last Confirmed - within each listener submessage, the Last Confirmed field contains the sequence number of the last message for which this listener confirmed delivery.
Unacknowledged Messages - number of messages pending for this listenener. The value is computed by subtracting the last sent sequence number from the last acknowledged sequence number.
===============================================================
For details, please refer to tibrvcmTransport_ReviewLedger() in "Chapter 11 Certified Message Delivery" of the RV C API Reference manual (or refer to the chapter "Certified Message Delivery" in eqivalent API reference manual).
Please note that the reviewLedger() calls were intended to be used from within the context of the running CM application; they were not intended to be used by an external application outside of the original runtime context. Hence, the best practice would be to gracefully shut down all relevant pub/sub applications first, then use the reviewLedger() call, by doing so, the results produced should be consistent.
Issue/Introduction
Is there any tool to review the CM Ledger file?
Feedback
Yes
No
Powered by
