Resolution:
If the ledger file was either copied from a CM system during runtime or was copied from a CM system, which
had not been shut down gracefully, the results produced by review ledger program could be inaccurate, as they did not precisely reflect the
CM runtime state.

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.

However, if the original application was allowed to shutdown gracefully, the values in the total_msg, total_size, seqno_last_sent
and listener.last_confirmed fields should be consistent.  

E.g. with our tests, In the graceful shutdown case we would have expected to see the following values:

    total_msg = 0
    total_size = 0
    seqno_last_sent = 100
    listener.last_confirmed = 100

instead of  listener.last_confirmed = 10, as was the case when "Ctrl C" the application.

We have another internal utility to review the ledger. If you have any questions, please send us your ledger file for review.

The cmlistener confirmed all messages, why did reviewledger report that there were unconfirmed messages?