13.6. What’s Fixed in 7.6.0

This section describes bugs fixed in Observability Framework 7.6.0. These are fixes since 7.5.0.

RTI® Connext® 7.6.0 is an early access release. See the Connext Versions and Lifecycle page for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

Note

Some fixes relevant to Observability Framework are documented in the RTI product where the fix was applied. See also the release notes for the Core Libraries and Admin Console.

[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.

13.6.1. [Critical] Potential crash when removing unready resources

A crash could have occurred when a resource was deleted before Collector Service had received all of the required metadata for the resource. This could happen in rare cases when a newly-created child resource was deleted before Collector Service fully processed the parent resource.

[RTI Issue ID OCA-422]

13.6.2. [Critical] Possible memory leak due to error in processing child resources

A memory leak could have occurred when deleting resources with a child resource registered multiple times to a parent resource. The duplicate registration of a child resource with a parent could occur in cases where resource updates were received out of order.

[RTI Issue ID OCA-414]

13.6.3. [Critical] Unbounded memory growth when using remote administration commands in Observability Framework

The use of remote administration commands in Observability Framework caused, in most cases, the leak of instances related to these commands. Leaking these instances led to an unbounded memory growth as commands were sent by Collector Service. Note that Collector Service sends commands automatically on discovering new applications, so the memory growth could occur even if no remote administration command was sent from the interface.

[RTI Issue ID OCA-411]

13.6.4. [Major] Query condition errors on discovering more than four applications simultaneously

On discovering new applications, Collector Service automatically triggers commands to discover initial application status. Due to resource limits, Collector Service did not track more than four simultaneous commands. If more than four applications were discovered before the commands were resolved, you would get the following error messages:

ERROR RTI_MonitoringForwarderCommandManager_populateCommonCommandHandlerFields:FAILED TO CREATE | Query condition for command
ERROR RTI_MonitoringForwarderCommandManager_getRequestResourceRegistryHandler:FAILED TO INITIALIZE | command handler for request_resource_registry command
ERROR RTI_MonitoringForwarder_requestResourceRegistryFromDestination:FAILED TO GET | Command handler for request_resource_registry command

These errors could be ignored since they did not affect data reception from those applications; however, the data may have been delayed for a few seconds. Collector Service now can track more than four commands simultaneously.

[RTI Issue ID OCA-413]

13.6.5. [Major] Potential timeout on commands addressed to more than one application

When a command was addressed to more than one application, it could return a timeout error, even if all the applications had received and processed the command. This behavior was caused by the instance management of the command responses that, depending on the reception timing, could have prevented Collector Service from processing all the responses to the command.

[RTI Issue ID OCA-383]

13.6.6. [Minor] RTI Collector Service sent samples that should have been discarded to the endpoints

The Collector Service (used by RTI Observability Framework and RTI Admin Console) processes samples upon receipt, prior to transmission to the endpoint. Previously, the Collector Service failed to discard these samples appropriately, resulting in their transmission to the endpoints instead of their proper disposal. Now, the Collector Service correctly discards the samples.

[RTI Issue ID OCA-428]