Certified Messages were repeatedly sent many times.
Article ID: KB0089876
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
This issue could be caused by duplicate sender CM names and the two CM senders sending the CM messages almost at the same time. If tested with two cmsender.java clients with the same cmname, you may not noticed this problem as the two CM messages were not sent at the same time.
If there are two listeners and they listen to the same subject and sent the CM messages in the message callback, the CM messages will be sent almost at the same time.
Resolution:
= = = = = = =
Since duplicated CM names is not supported, the behavior is unpredictable. You may run into additional unexpected behavior. In the case of a FT environment, it is suggested to put the RVFT layer in your application so that only the ACTIVE member can have live CM transport.
Description:
= = = = = = =
This issue could be caused by duplicate sender CM names and the two CM senders sending the CM messages almost at the same time. If tested with two cmsender.java clients with the same cmname, you may not noticed this problem as the two CM messages were not sent at the same time.
If there are two listeners and they listen to the same subject and sent the CM messages in the message callback, the CM messages will be sent almost at the same time.
Resolution:
= = = = = = =
Since duplicated CM names is not supported, the behavior is unpredictable. You may run into additional unexpected behavior. In the case of a FT environment, it is suggested to put the RVFT layer in your application so that only the ACTIVE member can have live CM transport.
Issue/Introduction
Certified Messages were repeatedly sent many times.
Feedback
Yes
No
Powered by
