Download Release Notes - Community RTI Connext Users

Transcript
4.12.36 TCP Transport's enable_keep_alive Property had no Effect on Server Sockets when Using TLS
4.12.36 TCP Transport's enable_keep_alive Property had no Effect on
Server Sockets when Using TLS Support
When using TLS Support with the TCP transport, and the enable_keep_alive property was set to 1, the
sockets created by the TCP server did not enable the TCP “keep alive” socket option. This issue did not
affect TCP client sockets. This problem has been resolved.
[RTI Issue ID COREPLG-273]
4.12.37 TCP Transport’s ‘keep_alive_*’ Properties had no Effect—Linux
Platforms Only
When the TCP Transport plugin’s keep_alive_time, keep_alive_interval, and keep_alive_retry_count
properties (only supported on Linux platforms) were set, they were not properly applied to TCP sockets.
This problem has been resolved.
[RTI Issue ID COREPLG-255]
4.12.38 TCP Transport’s ‘keep_alive_*’ Properties had no Effect when
Using TLS Support—Linux Platforms Only
When using TLS Support with the TCP transport, and the TCP transport’s keep_alive_time, keep_alive_
interval, and keep_alive_retry_count properties (only supported on Linux platforms) were set, they were
not properly applied to TCP sockets. This problem has been resolved.
[RTI Issue ID COREPLG-274]
4.12.39 TCP Transport Plugin's Connection Liveliness Stopped Working
In the 5.1.0.38 release, under certain circumstances the connection-liveliness feature may have stopped
working after a random amount of time. This problem has been resolved.
[RTI Issue ID COREPLG-308]
4.12.40 TCP Transport Plugin Opened UDPv4 Sockets when Running in
WAN Mode
In previous releases, the TCP transport plugin created unnecessary UDPv4 sockets when running in WAN
mode. This problem has been resolved.
[RTI Issue ID COREPLG-174]
54