2.2.6. RTI Admin Console
2.2.6.1. Remote debugging between 7.5.0 and 7.6.0 does not work
Previously when using the Remote Debugging feature in Admin Console, Monitoring Library 2.0 sent all telemetry data generated by a Connext application to Collector Service. Now, telemetry data is sent only if an active Admin Console session requests the data, reducing unnecessary network traffic and improving system efficiency.
This enhancement breaks compatibility between 7.5.0 monitored applications and 7.6.0 Collector Service, and vice versa. The reason is that 7.6.0 Collector Service sends commands that are not supported by 7.5.0 Monitoring Library 2.0 (so you cannot monitor 7.5.0 applications with 7.6.0), and 7.5.0 Collector Service does not support sending the command to enable remote debugging data from 7.6.0 Monitoring Library 2.0 (so you cannot monitor 7.6.0 applications using 7.5.0).
You can remotely debug 7.6.0 applications using 7.6.0 Connext only. Note that the remote debugging feature did not exist before 7.5.0, so you cannot use 7.6.0 Connext to remotely debug earlier Connext versions.
See Remote Debugging, in the 7.6.0 Admin Console User’s Manual, for more information.
2.2.6.2. Collector Service XML profile name changes for remote debugging
The following XML profile names changed from release 7.5.0 to 7.6.0:
SecureRemoteDebuggingin 7.5.0 is nowSecureRemoteDebuggingWANin 7.6.0NonSecureRemoteDebuggingin 7.5.0 is nowNonSecureRemoteDebuggingLANin 7.6.0
If you were using one of these profiles to launch the Collector Service docker image, you will need to use the new name.
The names changed to be consistent with other profile names. See Remote Debugging, in the Admin Console User’s Manual, for information on these profiles.