6.2.17. Entities

6.2.17.1. [Critical] Application may have hung when deleting a monitored DDS entity *

If RTI Monitoring Library 2.0 (previously called Observability Library) was enabled, you deleted a DDS entity (for example, by calling DDS_Publisher_delete_datawriter or a similar API), and periodic metrics were being collected for the same DDS entity, the application may have hung. The hang occurred because the deletion thread and the periodic thread took the same pair of semaphores in inverted order.

This hang is now fixed. Periodic metrics are not collected for an entity that is being deleted.

[RTI Issue ID MONITOR-580]

6.2.17.2. [Major] Monitoring Library 2.0 incorrectly collected both enabled and disabled DDS Entities *

In the previous release, Monitoring Library 2.0 (then called Observability Library) incorrectly collected both enabled and disabled DDS Entities if the library was enabled after creating the entities. Now, Monitoring Library 2.0 will only assert enabled DDS Entities, ensuring that disabled entities are not unnecessarily collected. Disabled DDS Entities are asserted when they are enabled.

[RTI Issue ID MONITOR-594]

6.2.17.3. [Major] Monitoring Library 2.0 did not assert disabled DDS Entities when the Entities were enabled *

If Monitoring Library 2.0 (previously called Observability Library) was enabled in an application and then DDS Entities were created disabled (by setting the entity_factory.autoenable_created_entities QoS setting to false), disabled Entities were not asserted by the library when they were enabled. This meant that these DDS Entities were never observed by Monitoring Library 2.0.

This issue is fixed. Disabled DDS Entities (and all their contained Entities) are now asserted after enabling.

[RTI Issue ID MONITOR-574]

* This bug does not affect you if you are upgrading from 6.1.x or earlier.