4.5.2. What’s Fixed in 6.1.1

4.5.2.1. Zoom Level in Routing Service Graph was Reset after an Update

The Routing Service graph’s zoom level and view position may have been changed when the graph was updated. This issue has been resolved. Now the zoom level will not be reset and the view position will not be changed when the graph is updated.

[RTI Issue ID ADMINCONSOLE-790]

4.5.2.2. Process View Showed Multiple Log Tabs

The Process view showed multiple Log tabs in some situations. For example, this occurred if you deleted and quickly recreated a DomainParticipant that contained Distributed Logger information. This problem has been resolved.

[RTI Issue ID ADMINCONSOLE-806]

4.5.2.3. Some Entities no Longer Appeared in Routing Service Graph after an Update

If DomainRoutes were disabled and then re-enabled, Admin Console’s Routing Service graph did not show all the entities. This issue has been resolved and updates will be correctly shown in the Routing Service graph.

[RTI Issue ID ADMINCONSOLE-903]

4.5.2.4. Admin Console Failed on Linux Platforms when Closing Windows with Embedded Web Content

Admin Console may have failed when closing windows that had embedded web content. The windows that were affected by this issue were the Help Contents and the Welcome Screen. This situation, which only happened on Linux systems, caused the application to be blocked.

The problem with the Help Contents windows happened when the help was not open in the browser but in a new Admin Console window. The problem with the Welcome Screen happened when closing an Admin Console window while the Welcome Screen tab was open. This problem may also have happened when closing Admin Console while the Entity Info tab was open. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-932]

4.5.2.5. QoS for Childless Publishers/Subscribers not Displayed

When a childless Publisher or Subscriber was selected, its QoS was not displayed. In previous versions, you may have worked around this problem by turning off the RTI Topics filter. This issue has been resolved, so this workaround is no longer necessary.

[RTI Issue ID ADMINCONSOLE-935]

4.5.2.6. Admin Console may have Reported a Mismatch that Should have been a Match

When using XCDR2 and appendable types, there were some circumstances in which Admin Console incorrectly showed a mismatch, that should have been a match. This issue has been fixed to show the right matching status.

[RTI Issue ID ADMINCONSOLE-939]

4.5.2.7. Admin Console Crashed when using Wayland Windowing System

Due to a known issue in OpenJFX™ 11, Admin Console crashed when using the Wayland windowing system. This issue has been fixed. Admin Console will use x11 instead of Wayland to avoid this problem. For more information about the OpenJFX issue, please see https://bugs.openjdk.java.net/browse/JDK-8210411.

[RTI Issue ID ADMINCONSOLE-941]

4.5.2.8. Admin Console Failed to Subscribe to Topics under Certain Circumstances

Admin Console failed to subscribe to topics under certain circumstances. As result, Admin Console indicated that it was subscribed to the topic when it was not. This issue has been fixed. Now if Admin Console fails to subscribe to a topic, a dialog will show the error.

[RTI Issue ID ADMINCONSOLE-943]

4.5.2.10. Crash when using an Unsupported GTK Version

Using an unsupported GTK version may have caused Admin Console to crash. This issue has been fixed. Admin Console will notify you during startup if it detects an unsupported GTK version. Admin Console will still run, but you may see problems due to the unsupported GTK version.

See Compatibility for the minimum GTK version.

[RTI Issue ID ADMINCONSOLE-949]

4.5.2.11. Process Information showed Incorrect Version Number for RTI Connext Micro

The Process Information panel did not correctly display the version number for RTI Connext Micro. This problem has been resolved.

[RTI Issue ID ADMINCONSOLE-965]

4.5.2.12. Domain View Graph Stayed Open after User Manually Left the Domain

If you manually left a Domain while its Domain View graph was open, that graph remained open and displayed invalid information. This issue has been fixed. Now when you manually leave a Domain, the graph for that Domain will close, since Admin Console is no longer connected to that Domain.

[RTI Issue ID ADMINCONSOLE-966]

4.5.2.13. Routing Service Graph Showed Wrong Names for Some Entities

Routing Service entities whose names contained a “/” character may not have displayed correctly in the Routing Service graph. This issue has been fixed. Now even if the Routing Service entity contains this specific character, the name shown in the graph will be correct.

[RTI Issue ID ADMINCONSOLE-969]

4.5.2.14. Admin Console Views Sometimes Obscured

In some views, the content was obscured by a description of that view’s entity if the view was anchored (unlinked from tracking changes to the graphical selection). This issue has been fixed.

[RTI Issue ID ADMINCONSOLE-972]

4.5.2.15. Admin Console showed writer_depth in QoS Tree View when it was not Available

Admin Console always showed the default value for writer_depth in the QoS Tree View. However, this field is not sent over the wire, so Admin Console has no way to know its real value. Therefore writer_depth has been removed from the QoS Tree View.

[RTI Issue ID ADMINCONSOLE-973]

4.5.2.16. Admin Console may have Failed when Providing Process ID for Some Processes

Admin Console may have failed when providing the Process ID on some architectures that use a larger Process ID. This issue has been fixed.

[RTI Issue ID ADMINCONSOLE-975]

4.5.2.17. Incorrect Units Displayed in Routing Service User Interface

A column that shows the latency experienced by Routing Service components was mislabeled as microseconds, when it was actually showing milliseconds. The column label as been corrected.

[RTI Issue ID ADMINCONSOLE-982]

4.5.2.18. Failure to Import Discovery Information if topic_data Present

Admin Console failed to import discovery data files if they contained non-empty <topic_data> XML elements. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-986]

4.5.2.19. High CPU usage by Admin Console

Admin Console incorrectly identified too many fields as participating in the key of the data type. Also, the Instance Table view attempted to add all key fields as columns. If this behavior was combined with finding too many keys, Admin Console experienced high CPU consumption. This issue has been resolved.

[RTI Issue ID ADMINCONSOLE-995]

4.5.2.20. Admin Console did not correctly delete Publisher and Subscriber Entities

There was a problem that caused the Publisher and Subscriber entities discovered by Admin Console to remain created in the different Admin Console views even when they were no longer present in the system. This issue has been resolved; Publisher and Subscriber entities are now correctly removed.

[RTI Issue ID ADMINCONSOLE-1000]

4.5.2.21. Admin Console may have failed on Ubuntu 16.04 LTS Systems

Admin Console may have failed on Ubuntu® 16.04 LTS systems, due to a problem with JavaFX® and its web engine. As result of this failure, Admin Console closed without notifying the user. This problem has been resolved.

[RTI Issue ID ADMINCONSOLE-1019]