Solution Control Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
When both primary and backup SCS are running and auto-restart is enabled for SCS, if LCA stops one of the SCS instances, that SCS now stops as expected. Previously in this scenario, a race condition occurred in which LCA received RequestAppStartupInfoChanged before SCS actually stopped and after RequestStopApplicaton was received, and LCA stopped SCS and then incorrectly restarted it automatically. (MFWK-19393)
LCA now properly sends the notification that NTP is running with TLS between SCS and LCA only once, when the connection is first made. Previously, LCA sent the notification continuously through the process. (MFWK-19357)
When distributed Solution Control Servers are configured, master SCS CPU usage no longer increases when another SCS sends its own status as Stopped. This inter-server notification can be seen in logs as a statement such as:
#### SCSDistrib[<distributed SCS name>] ==> App '<same distributed SCS name>' status=APP_STATUS_STOPPED
Previously in this scenario, the CPU usage of the master SCS increased. (MFWK-19230)
No special procedure is required to upgrade to release 126.96.36.199.