4.5.2. What’s Fixed in 6.1.0¶

This section describes bugs fixed in 6.1.0. These fixes have been made since 6.0.1 was released.

4.5.2.1. Exported discovery data was missing RTI Service information¶

Discovery data exported from Admin Console was missing information about the Service QoS. After importing this data into Admin Console, the missing data caused Admin Console to display a generic process view instead of an RTI service-specific view. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-775]

4.5.2.2. Data representation mismatch in matching graph for Routing Service builtin topics¶

Admin Console could not correctly subscribe to administration and monitoring topics from Routing Service. As a result, when Admin Console created subscriptions to Topics whose name started with “rti/service/admin/” from Routing Service, there was a data representation error in the match graph. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-795]

4.5.2.3. RTI topics were not checked for request/offered mismatches¶

Topics created by RTI products such as Routing Service and other services were not checked by Admin Console for their request/offered state. While this was previously intentional, this release reverses that decision in order to help debug use cases involving these Topics. Now Admin Console will check for mismatches in the request/offered state of these Topics.

[RTI Issue ID ADMINCONSOLE-796]

4.5.2.4. DDS Domains in DDS Logical View were not sorted¶

DDS Domains appearing in the DDS Logical view were not properly sorted by their Domain ID. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-801]

4.5.2.5. Routing Service user interface missing data¶

In certain circumstances, the user interface shown for Routing Service may have been incomplete. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-803]

4.5.2.6. Rows in Distributed Log View not correctly colorized on Windows systems¶

Rows in the Distributed Log view were not correctly colorized on Windows systems. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-805]

4.5.2.7. Multiple Log tabs could appear¶

The Process showed multiple Log tabs under certain circumstances. This could have happened when the DomainParticipant containing the Distributed Logger information was deleted and quickly recreated. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-806]

4.5.2.8. Recording and Replay Service interface anomalies¶

The information and configuration tabs of both the Recording and Replay services sometimes did not show accurate and up-to-date information. This happened if the interface was opened very shortly after the service was discovered by Admin Console. These issues have been resolved.

[RTI Issue ID ADMINCONSOLE-813]

4.5.2.9. Extra DomainParticipants created when subscribing to topics¶

Starting with 6.0.0, Admin Console created a new DomainParticipant every time a Topic was subscribed to/visualized. Normally, Admin Console attempts to reuse existing DomainParticipants wherever possible. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-814]

4.5.2.10. Incorrect display of a data structure that used a non-keyed structure as its key¶

This issue happened when you had this situation:

struct A { long field; }; // no key
  struct B {
  @key
  A a;
};

Struct B indicated that struct A should be used as its key, but A didn’t identify any of its fields as a key. This should cause all the fields in A to be treated as keys. However, Admin Console failed to identify this case and marked none of A’s fields as keys. This resulted in a display that indicated no key fields were found, or presented other confusing information.

This problem has been resolved. Now in this situation, when Admin Console displays struct B, it will show that all the fields in A are keys.

[RTI Issue ID ADMINCONSOLE-817]

4.5.2.11. Host IP address appeared as 0.0.0.0¶

When using IPv4, the host’s address was displayed as 0.0.0.0. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-819]

4.5.2.12. Incorrect process information shown for local subscriptions after restart¶

When subscribing to Topics, Admin Console displays its own process in the Physical view. Previously, upon restart, the process information shown was that of the original process (such as the ID) and not the current process. Because of that, the process name did not contain “This Admin Console” as it should (this is done to make it easier to understand if the current Admin Console is the one subscribing or another instance of Admin Console). This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-876]

4.5.2.13. Typo in Admin Console log¶

The Admin Console log contained a misspelling, “associtaed.” This typographical error has been fixed.

[RTI Issue ID ADMINCONSOLE-882]

4.5.2.14. Security log level “critical” was not usable¶

When configuring the log level for the security logger in Admin Console, the level “critical” was not usable due to a typo. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-930]

4.5.2.15. Admin Console showed wrong maximum annotation for ‘unsigned long long’¶

If you used an ‘unsigned long long’ in your type, such as:

struct foo{
    unsigned long long u64;
};

Admin Console displayed the following IDL:

struct foo {
    @max(-1)
    unsigned long long u64; //@ID 0
};
//@Extensibility EXTENSIBLE_EXTENSIBILITY

The maximum annotation was not correct in this display. This issue only affected the IDL display in Admin Console.

This issue has been fixed; now the IDL for this type will look like this:

struct foo {
    unsigned long long u64; //@ID 0
};
//@Extensibility EXTENSIBLE_EXTENSIBILITY

[RTI Issue ID CORE-9846]