T5BusEIPS: Idle TCP connections are not automatically closed.

• Related Articles

• Exchanging a driver may result in an intermediate driver configuration file causing configured connections to be lost

  Summary When a driver is exchanged with a new driver, the driver configuration of the new driver is opened automatically. With some drivers that use TCP communication, the connections that are created in the driver configuration during the exchange ...

• zenLogSrv: no TCP keep alive for listening socket

  Description The TCP server of zenLogSrv.exe did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep alive for the ...

• Remote-Transport: no TCP keep alive for listening socket

  Description The TCP server of process zensysSrv (used for remote transport) did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP keep alive for the ...

• In Docker-Compose: no TCP keep alive for listening socket, port 50780

  Description In Docker the TCP server of process zenLogSrv.exe did not send a TCP keep alive to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep ...

• MELSECA: When primary server comes back online (dominant) the MELSECA driver on the standby server is not stopped (keeps the TCP connection alive) and the MELSECA driver on primary can no longer connect to the PLC and therefore the variable gets invalid

  Summary TCP Connections are not closed on Driver stop Description TCP Connections are not closed on Driver stop Issue Number: 221250 Fixed on Date: 8.7.2020 Versions: 8.10 0 BUILD 67223 | 8.20 0 BUILD 67231