Local Control Agent 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features or enhancements:
- Support for the Windows Server 2016 64-bit operating system. See the Supported Operating Environment: Framework page for more detailed information and a list of all supported operating systems.
- As of 9/26/17, Local Control Agent supports the Microsoft Hyper-V Server 2016 virtualization platform. Refer to the Supported Operating Environment: Display by Product, Operating System, and Other page for more detailed information and a list of all supported virtualization platforms.
This release contains the following resolved issues:
When TLS is enabled between SCS and LCA, LCA now processes the data sent and received through sockets. Previously in this scenario, some data was sent or received before TLS was established, and the data was not processed properly. As a result, the following error message was generated: LCALIB: Can't send to socket. (MFWK-17697)
On the Solaris platform, logs are now generated properly. Previously, a log segmentation problem prevented some input/output logs from being generated. (MFWK-18591)
LCA now stops Applications and reports them as STOPPED accordingly. Previously, an Application would stop responding while in Stop Pending state, while LCA would wait for the Application to stop. The only way to regain control of the Application was to restart LCA. (MFWK-18552)
LCA now stops processing heartbeat messages from an Application when heartbeat-timeout is set to zero (0). When the option value is greater than 0, LCA starts processing heartbeat messages again. Previously, if heartbeat-timeout was equal to 0, the Application kept polling for heartbeat messages, but LCA did not process any. (MFWK-18194)
No special procedure is required to upgrade to release 184.108.40.206.