5.9. Logging
5.9.1. [Major] Modern C++ Distributed Logger Options header incorrectly included generated header file *
The Modern C++ Distributed Logger implementation included a header file
in DistLoggerOptions.hpp that should not be needed. The header file
distlogSupport.h is no longer required.
[RTI Issue ID DISTLOG-237]
5.9.2. [Major] Misleading log message when sending specific number of bytes through socket *
In 7.2.0, a misleading warning was printed when Connext sent some specific number of bytes through the socket. The log message would look like, or similar to, this one:
NDDS_Transport_UDP_send:SENDING FAILURE | Inconsistent message size. Written bytes (<inconsistent_value>) and bytes to send (<expected_value>)
The <inconsistent_value> could be 0 or a big number. This warning is
now only printed when Connext has actually failed to send a message
through the socket.
[RTI Issue ID CORE-14007]
5.9.3. [Major] Missing logging on the standard output for Windows GUI applications
Windows graphical user interface (GUI) applications using Connext libraries were not able to print log messages to a console through the standard output. The console was opened, but the messages did not appear. Log messages are now displayed properly in the console.
[RTI Issue ID CORE-14061]
5.9.4. [Minor] Incorrect error message when setting inconsistent ReaderDataLifeCycleQosPolicy values
The error messages that were printed when inconsistent values were used
in the ReaderDataLifeCycleQosPolicy referenced the wrong fields. For
example, when the value for autopurge_nowriter_samples_delay was set
to a value that was out of bounds, the error message incorrectly
referenced autopurge_disposed_samples_delay. These messages now
reference the correct fields.
[RTI Issue ID CORE-14148]
5.9.5. [Minor] Log messages truncated below maximum size of 1024 bytes *
Some log messages were truncated below the maximum size of 1024 bytes if
NDDS_Config_LogPrintFormat had been configured to print the
timestamp, log level, thread ID, category, or activity context. Log
messages are now logged with the full 1024 bytes.
[RTI Issue ID CORE-14105]
5.9.6. [Trivial] Error message that was printed when failing to allocate the writer buffer pool was wrong *
The error message that was printed when failing to allocate the writer buffer pool was wrong. It printed the incorrect resource limit value and the size of the buffers in the pool was always printed as 0.
Previous message:
PRESTypePluginDefaultEndpointData_createWriterPool:ALLOCATION FAILURE | 9 initial samples with size 0 in writer buffer pool. Consider setting dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size if your type has a large or unbounded max serialized size or reduce initial_samples.
New message:
PRESTypePluginDefaultEndpointData_createWriterPool:ALLOCATION FAILURE | 32 initial samples with size 2147482620 in writer buffer pool. Consider setting dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size if your type has a large or unbounded max serialized size or reduce initial_samples.
[RTI Issue ID CORE-14218]
5.9.7. [Trivial] Missing space between Activity Context and message text if Logging Category was printed *
If a log message belongs to the Security or Discovery category and your application logging was configured to print the Activity Context and the Logging Category, then there was a space missing between the end of the Activity Context and the beginning of the message. For example:
WARNING [0x01017774,0xFF40EEF6,0xEC566CA8:0x000001C1{Domain=2}|ENABLE|LC:Discovery]NDDS_Transport_UDPv4_Socket_bind_with_ip:0X1EE6 in use
Now, a space is always printed:
WARNING [0x01017774,0xFF40EEF6,0xEC566CA8:0x000001C1{Domain=2}|ENABLE|LC:Discovery] NDDS_Transport_UDPv4_Socket_bind_with_ip:0X1EE6 in use
[RTI Issue ID CORE-14262]
* This bug does not affect you if you are upgrading from 6.1.x or earlier.