RVCM Explicit confirm stops working.
Article ID: KB0090564
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = = =
By overriding automatic confirmation, the consumer assumes responsibility for explicitly confirming each inbound certified message. If the consumer did not acknowledge any message for a period of time, the publisher will send an acknowledgement request on a per subject basis to the recorded inbox of the subscriber.
When the listening transport receives a request for confirmation, it checks its ledger and reconfirms receipt of the message that it has ALREADY confirmed. If due to some exception, one cm message was not confirmed, that is the confirm call was not called, it will cause all subsequent confirmations blocked on CM receiver side and all subsequent messages penning on CM sender side.
Resolution:
= = = = = = =
Submit both the cmsender and cmlistener ledger files to TIBCO Messaging Support for review.
Description:
= = = = = = = =
By overriding automatic confirmation, the consumer assumes responsibility for explicitly confirming each inbound certified message. If the consumer did not acknowledge any message for a period of time, the publisher will send an acknowledgement request on a per subject basis to the recorded inbox of the subscriber.
When the listening transport receives a request for confirmation, it checks its ledger and reconfirms receipt of the message that it has ALREADY confirmed. If due to some exception, one cm message was not confirmed, that is the confirm call was not called, it will cause all subsequent confirmations blocked on CM receiver side and all subsequent messages penning on CM sender side.
Resolution:
= = = = = = =
Submit both the cmsender and cmlistener ledger files to TIBCO Messaging Support for review.
Issue/Introduction
RVCM Explicit confirm stops working.
Feedback
Yes
No
Powered by
