Jump to: navigation, search

Configuration Server 8.5.x Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
11/26/14 General X X X X

Helpful Links

What's New

This release contains the following resolved issues:

  • Enhanced Security of Encrypted Configuration Database Password: The password for the Configuration Database can now be encoded using an asymmetric encryption algorithm, with the encryption and decryption keys stored in external files.
  • The enable-thread option in the [log] section of the Configuration Server Application template is now set to false, the default value. If you want to use the log throttling feature with Configuration Server, you must explicitly change the value of this option.

Resolved Issues

This release contains the following resolved issues:

Configuration Server no longer terminates unexpectedly when attempting to generate a log message about an ADDP timeout expiring on any of its connections (for example, STANDARD 00-07041 Socket [X] is not responding within [n] milliseconds, remote socket [Y].). This issue was specific to the 32-bit Linux platform. Previously in this scenario, Configuration Server sometimes terminated unexpectedly on the 32-bit Linux platform. (MFWK-16314)

Configuration Server now starts correctly and no longer terminates unexpectedly shortly after startup when the Configuration Database password is encrypted by itself (confserv -p <name of Configuration Database section> <password> on the command line, and encryption=true in the [Configuration Server] section of the configuration file). Previously in this scenario, Configuration Server sometimes terminated unexpectedly shortly after startup. (MFWK-16242)

When the primary master Configuration Server loses its connection to DB Server, it switches to Read Only mode. It now correctly switches back to fully operational mode when the connection is restored, even in those scenarios that also involve a loss of connection between SCS and LCA on the Configuration Server host. Previously in these scenarios, Configuration Server sometimes did not return to fully operational mode. (MFWK-16168)

Configuration Server now functions normally in the following scenario:

  • The connection with the Configuration Database was lost and then restored.
  • The database operation in process prior to the disconnection was completed unsuccessfully.
  • The force-reconnect-reload option is set to true.

Previously in this scenario, Configuration Server sometimes repeatedly disconnected all clients and tried to reload content from the Configuration Database. After a number of attempts, Configuration Server terminated unexpectedly.

(MFWK-16110, MFWK-16046)


Configuration Server Proxy and the backup master Configuration Server now support runtime configuration of ADDP parameters for their connections to the master Configuration Server. In addition, both the primary and backup master Configuration Servers are now able to handle a runtime reconfiguration of the ADDP timeout on their connections with Message Server. Previously, these changes took effect only after a restart. (MFWK-12270)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on November 18, 2015, at 19:03.
Comments or questions about this documentation? Contact us for support!