5.7. Logging

5.7.1. [Minor] DomainParticipants in same application may have have had different verbosities for logging security messages *

The last DomainParticipant explicitly that set the plugin-specific logging.verbosity property (set by you, in the QoS settings) will apply that setting to all the DomainParticipants within the application and all security-related messages logged from the Connext libraries. This is the behavior in all Connext releases, except for 7.2.0.

Connext 7.2.0 introduced support for running a combination of DomainParticipants from the Builtin Security Plugins library (nddssecurity) and the Lightweight Builtin Security Plugins library (nddslightweightsecurity) within the same application. In 7.2.0, the logging verbosity (for all security-related messages) of all the DomainParticipants belonging to the same security library was determined by the last DomainParticipant of that library (as opposed to the last DomainParticipant within the application) created by your application.

Connext 7.3.0 reverts this behavior. The logging verbosity for all security-related messages is again determined by the last DomainParticipant that your application creates.

[RTI Issue ID SEC-2368]

5.7.2. [Trivial] Typo in “non-compliant DDS Security implementation” log message

There was a typographical error in the “non-compliant DDS Security implementation” warning message that you see when interoperating with certain DDS Security vendors:

This is likely caused by a non-compliantDDS Security implementation.

Notice there was a space missing after compliant. This problem only affected 7.2.0 and 6.1.2.10.

[RTI Issue ID SEC-2248]

* This bug does not affect you if you are upgrading from 6.1.x or earlier.