.. include:: ../vars.rst .. _section-known-issues: Known Issues ============ .. note:: For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com/. |AC_HEADING| may require installing legacy Java SE 6 Runtime on macOS platforms ------------------------------------------------------------------------------- On some macOS systems, you may see this message: .. code-block:: none To open |AC| you need to install the legacy Java SE 6 runtime. This may also cause the right-click menu for the *Routing Service* graph to not appear. This happens because |AC| may require the legacy Java 6 SE provided by Apple to work correctly; installing it from the Apple support portal should fix the issue. You can find the Java 6 runtime provided by Apple here: https://support.apple.com/kb/DL1572?locale=en_US. [RTI Issue ID ADMINCONSOLE-911] Preferences dialog shows error message -------------------------------------- The Preferences dialog will show an error message when viewing the preference for XML -> XML Files -> Editor: .. code-block:: none "org.eclipse.wst.sse.ui.preferences.editor not found." This error message has no affect on functionality and will be removed in a future release. [RTI Issue ID ADMINCONSOLE-199] Limited to single instance of |AC_HEADING| on macOS platforms ------------------------------------------------------------- On macOS platforms, only one instance of |AC| can be run at a time. This limitation is not present on other platforms. [RTI Issue ID ADMINCONSOLE-403] Limited support for keyed, unbounded sequences ---------------------------------------------- There is limited support when using a data type that contains a field that is an unbounded sequence and that field participates in the key. The limitation is that only a subset of the total possible (2,147,483,647) sequence elements can be used. This limitation protects against high memory and CPU consumption by the application. The limited number of fields chosen to represent the key can be seen in the Topic Data tab and when selecting data instances for the Time Chart. [RTI Issue ID ADMINCONSOLE-399] Interaction between |AC_HEADING| and RTI Recording Console ---------------------------------------------------------- This issue only applies if you are using any version of |AC| and Recording Console (which only exists before 6.0.0) at the same time, and you have configured |AC| to join domain ID 99. In this scenario, do not use |AC| to pause or disable any Recording Console services (their names begin with "RTI-Recorder-" or "RTI-Replay-"). Doing so may cause an error in Recording Console. [RTI Issue ID RECORD-253] |AC_HEADING| incompatible with RTI Routing Service configurations that use DomainParticipant Name QoS ----------------------------------------------------------------------------------------------------- This issue only occurs when using |AC| with *RTI Routing Service* 5.2 or older. |AC| will not correctly display or administer instances of RTI Routing Service that have overridden the default DomainParticipant QoS participant_name. These names are used to identify the process as *RTI Routing Service*. You may see error messages in |AC|'s log such as: .. code-block:: none expecting process model : RoutingService : corresponding to instance handle : {X} : to be a Routing Service instance when it is not cannot add monitoring capabilities for the RoutingService since the model was not found for instance handle : {X} unable to find a DomainRoute named : {Domain Route name} : associated with RoutingService : {Routing Service name} unable to find a Session named : {Session name} : associated with RoutingService : {Routing Service name} : and DomainRoute : {Domain Route name} unable to find an AutoRoute named : {Auto Route name} : associated with RoutingService : {Routing Service name} : and DomainRoute : {Domain Route name} : and Session : {Session name} unable to find a Route named : {Route name} : associated with RoutingService : {Routing Service name} : and DomainRoute : {Domain Route name} : and Session : {Session name} [RTI Issue ID ADMINCONSOLE-270] |AC_HEADING| views restored when |AC_HEADING| is restarted ---------------------------------------------------------- |AC| will restore views (such as the Health view) each time the application is restarted. For example, if you closed the DDS Data Type view during the previous session, then it will be re-opened the next time you open |AC|. (Previously, it would remain closed.) This behavior is a workaround for an issue |AC| is experiencing: without restoring the views, some of them would be hidden behind each other. |AC_HEADING| potential crash on Linux systems when security is enabled ---------------------------------------------------------------------- Applications using the *RTI Security Plugins* may fail in systems with a default OpenSSL version prior to 1.1.1 (such as SUSE Linux Enterprise Server 12 SP2). This happens, for example, with |AC|. A workaround for this issue is to set the LD_PRELOAD environment variable to: .. code-block:: none export LD_PRELOAD=$NDDSHOME/resource/app/lib/x64Linux2.6gcc4.4.5/libcrypto.so.1.1:$NDDSHOME/resource/app/lib/x64Linux2.6gcc4.4.5/libssl.so.1.1:$LD_PRELOAD See Section "9.1.1, Dynamic Linking" in the *RTI Security Plugins User's Manual* for more information. [RTI Issue ID HERCULES-481]