.. _section-known-issues:


Known Issues
============

.. note:: For an updated list of critical known issues, see the Critical Issues List on
   the RTI Customer Portal at https://support.rti.com/.


Cloud Discovery Service does not terminate when its internal DomainParticipant does not initialize properly
-----------------------------------------------------------------------------------------------------------
|CDS| creates an internal |DP| that reserves the *participant_id* 0, on domain ID 0.
This |DP| is required by |CDS| to relay the participant discovery announcements.
If the *participant_id* 0 for domain ID 0 is already being used by another
|CONNEXT| application, |CDS| throws errors but doesn't terminate.

Although such a |CDS| instance is running, it won't be able to relay any participant
discovery announcements. A simple workaround is to ensure that |CDS| is always
the first |CONNEXT| application started on a given machine.

[RTI Issue ID CDS-143]

Some tags in the XML configuration must be grouped in a strict order
--------------------------------------------------------------------

The XML validator tools |CDS| uses to validate XML configuration files adhere
to the XML 1.0 specification, which doesn't offer a way of defining collections
of unordered tags that are both bounded and unbounded in occurrences.

This limitation is no longer present in XML 1.1. However, there are no C or C++
validators compliant with the XML 1.1 specification at the time of writing.

[RTI Issue ID CORE-14178]