Description:
Dear GridServer Users,

We just released HF-14 for Gridserver 5.1.2.

Closed Issues in 5.1.2_hotfix14 (This Release):

Affected Components for 5.1.2_hotfix14

The following components are updated by this hotfix:
Manager
Engine
Java Driver
Java Services
.NET Driver
.NET Services
C++ Driver
C++ Services

================================================================================
Closed Issues in 5.1.2_hotfix14 (This Release)


Admin Interface

GS-11514
A Daemon logged in with a corrupt config.xml file resulted in searches on the
Engine Admin page to fail, and certain EngineDaemonAdmin API calls to fail. The corrupt file is now ignored, and replaced with a good one when the Daemon is configured from the Daemon Admin page.



C++ Specific

GS-11495
If a C++ Driver started up and was unable to open a port for the embedded fileserver, various problems could occur. If using DDT or Data References, the following error would occur: 'java.net.MalformedURLException: no protocol'. Now if this happens, and DDT is enabled, the Driver will exit with exit code 1. If
DDT is not enabled, it will proceed, but any calls to create Data References with throw an Exception.



Configuration and Repository

GS-11440
If the Daemon Admin External Tool URL was saved with a URL that had multiple request parameters, the URL was saved incorrectly. This resulted in the Manager failing to start-up properly on the next restart.


Database

GS-11452
When making a query using the reporting database pages, some types of failures result in an unresponsive Broker, requiring a restart.


Engine Daemon-Windows

GS-11561
Currently, when a Windows Daemon is migrated from one Grid to another, the JRE is not synchronized if the Director hostname configured on the Daemon does not match, case-sensitive, the hostname as configured on the Director. This comparison is now case-insensitive.


Stability,Fault Tolerance

GS-11545
If a user logged in using capital letters in the username, or if Kerberos was enabled and the username had capital letters in Active Directory, LDAP User information was not cached. This resulted in very slow page loads and poor driver performance.


Upgrade and Migration

GS-11442
Improvements were made to the Engine JRE synchronization process. These changes are meant to facilitate upgrades from grids which use older JREs that are no longer supported.

GS-11470
Some internal changes were made to simplify future upgrades. These do not modify any existing behavior.

GS-11556
JRE synchronization from the Director has been added for UNIX engines in order to simplify upgrades to future versions. It is disabled by default.