14.4. What’s Fixed in 7.3.0 LTS

This section describes bugs fixed in Cloud Discovery Service 7.3.0 LTS. These are fixes applied since 7.2.0.

For information on what was fixed in releases 7.0.0, 7.1.0, and 7.2.0, which are also part of 7.3.0 LTS, see Previous Releases.

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

14.5. Crashes

14.5.1. [Critical] Cloud Discovery Service crashed if DomainParticipant update, send, or delete operations overlapped

This issue was fixed in version 7.2.0 but not documented at that time.

Cloud Discovery Service could have crashed if any of the following operations overlapped for a DomainParticipant:

Update: Occurs when Cloud Discovery Service receives an updated announcement from a previously seen DomainParticipant.
Send: Occurs when Cloud Discovery Service processes an incoming announcement from a DomainParticipant and the associated send job is being executed.
Delete: Occurs when Cloud Discovery Service receives a dispose or detects liveliness expiration for a DomainParticipant.

The crash was caused by an issue with state management when these operations were executed in parallel.

[RTI Issue ID CDS-239]

14.6. Other

14.6.1. [Minor] Fourth digit of product version not logged by Cloud Discovery Service at startup

The Cloud Discovery Service executable did not log the fourth digit (revision number) of the product version upon service start. As a result, any patches were indistinguishable from the base version.

[RTI Issue ID CDS-195]

14.6.2. [Minor] Restricting domains using command-line arguments required use of both -allowDomain and -denyDomain arguments

The -allowDomain and -denyDomain command-line arguments for Cloud Discovery Service allow you to restrict which domains the service operates on. The XML tag equivalents (<allow_domain_id> and <deny_domain_id>) allow use of just one of these tags, while the other tag uses its default; the same was not true for the command-line arguments.

This led to a usability inconsistency where using the command-line arguments -allowDomain and -denyDomain required use of both tags at the same time; otherwise, the values passed were not applied. Now, using any one of the arguments causes the other argument to use its default, while the passed value is now applied correctly.

[RTI Issue ID CDS-183]