AccessICCP: high cpu load on startup and high cpu load on connect of an ICCP client results in no connection being established

AccessICCP: high cpu load on startup and high cpu load on connect of an ICCP client results in no connection being established

Description

When connecting via the ICCP/TASE.2 protocol, the connection will not be established if a high CPU load occurs when starting the Process Gateway or when connecting an ICCP client. This can happen due to the initialization of a large number of variables. The ICCP gateway receives a COTP CR and sends the COTP CC delayed. In this case the timeout for the COTP CC is exceeded.

This behavior has been changed.

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 8.10 or higher.


Item ID: 236918
Version: 8.10 Build: 80844