6.14. Known Issues with RTI Monitoring Library

The following known issues occur in RTI Monitoring Library, not in RTI Monitoring Library 2.0.

6.14.1. Problems with NDDS_Transport_Support_set_builtin_transport_property() if Participant Sends Monitoring Data

If a Connext application uses the NDDS_Transport_Support_set_builtin_transport_property() API (instead of the PropertyQosPolicy) to set built-in transport properties, it will not work with Monitoring Library if the user participant is used for sending all the monitoring data (the default settings). As a workaround, you can configure Monitoring Library to use another participant to publish monitoring data (using the property name rti.monitor.config.new_participant_domain_id in the PropertyQosPolicy).

[RTI Issue ID MONITOR-222]

6.14.2. Participant’s CPU and memory statistics are per application

The CPU and memory usage statistics published in the DomainParticipant entity statistics topic are per application instead of per DomainParticipant.

[RTI Issue ID CORE-7972]

6.14.3. ResourceLimit channel_seq_max_length must not be changed

The default value of DDS_DomainParticipantResourceLimitsQosPolicy::channel_seq_max_length can’t be modified if a DomainParticipant is being monitored. If this QoS value is modified from its default value of 32, Monitoring library will fail.

[RTI Issue ID MONITOR-220]