14.4. What’s Fixed in 7.1.0

14.4.1. Cloud Discovery Service internal state issues caused increase in network traffic in certain situations

Cloud Discovery Service uses internal buffer pools to store the incoming participant announcements. Due to an issue with the state management, there were certain instances where an incoming announcement could have been reclassified as an update, even when there was no change in its contents. This caused the resend mechanism (if configured) to trigger additional resends, resulting in increased network traffic. The issue has been resolved.

[RTI Issue ID CDS-199]

14.4.2. <output_capacity_allocation> XML tag not parsed from configuration

Cloud Discovery Service didn’t parse the XML tag <output_capacity_allocation> when specified by the user in XML. As a result, users were unable to control the capacity allocation for the flow controller via XML. This issue has been resolved.

[RTI Issue ID CDS-198]

14.4.3. Discovery did not complete when using Real-Time WAN and multiple locators

When using a DomainParticipant with multiple RTI Real-Time WAN Transport locators, sometimes Cloud Discovery Service mixed up the locators and they were not resolved correctly. This caused the discovery process to never complete. This problem has been resolved.

[RTI Issue ID CDS-172]