Jump to: navigation, search

Solution Control Server 8.5.x Release Notes

Solution Control Server is part of 9.x starting in
Release Date Release Type Restrictions AIX Linux Solaris Windows
12/22/17 General X X X X

Helpful Links

What's New

This release contains the following new features or enhancements:

  • You can now set a timeout for Solution Control Server to expect a TCP success or failure response from the Configuration Server to which it is connecting. To set the timeout, use the new command-line parameter -cfglib-connect-tmout <time in seconds>, or use the corresponding new option cfglib-connect-tmout in the configuration file. The default value of this option is 20 seconds, and it is applied by Solution Control Server if nothing else is configured. For more information, refer to the Framework Deployment Guide for the new command-line parameter, or to the Framework Configuration Options Reference Manual for the new option.

Resolved Issues

This release contains the following resolved issues:

Solution Control Server can now better handle unstable network conditions when it tries to restore its sessions with Configuration Server. Previously in this scenario, Solution Control Server tried to reconnect but sometimes did not complete its connection attempt, did not make any more attempts, and remained disconnected until restarted. (MFWK-19062)

Solution Control Server now properly sends the email as directed by the Alarm Reaction associated with an Alarm Condition configured to report the disconnection of Solution Control Interface, and generates the following message correctly: CGCLLConnector: already connected. Handle is <id>. only once with the correct id. Previously in this scenario, the Solution Control Server did not send the email, and continuously generated the message with the same id, as if in a loop. (MFWK-18809)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last modified on December 22, 2017, at 12:17.


Comment on this article:

blog comments powered by Disqus