Description:
Dear GridServer Users,

We just released HF-7 for GridServer 6.0.2.

Closed Issues in 6.0.2_hotfix07 (This Release):

.NET Specific

GS-12087
Shared Directory DDT did not work on the .NET Driver.


Communication and Network

GS-11967
If an Engine was logged off and then logged into a Broker while a heartbeat was
in progress, it was possible for that heartbeat to fail and cause the Engine to
log off again. Now any heartbeat failure due to a connection being closed no
longers results in a logoff.


Documentation

GS-11817
Errors in the hotfix uninstall procedure in the readme were corrected.


Engine Daemon-Windows

GS-12209
Windows Engines can now support more than 64 cores.


GUI

GS-12101
The 'Background of Status Row' setting was not maintained after a Manager
restart if a hex color value was used.


Routing and Balancing

GS-11631
When a Task reservation expired, the pending Task count used by the Engine
balancer did not get updated, resulting in such problems as idle Engines not
being shared to work on such Tasks.


Security

GS-11637
When using Kerberos for authentication on a case-insensitive LDAP directory,
drivers would fail login if the username had a capital letter, with a log
message such as 'Invalid driver user name; driver user name is set to Thurston
but driver SPNEGO authentication user name was thurston.' This check is now
case-insensitive.


Services

GS-11658
The SLA Scheduler Setting reverted to "False" on a restart of a Standalone
Broker.

GS-11815
The Manager Configuration > Service > Service Rescheduler settings were not
properly saved when changed, and would be reset to defaults on Broker restart.

GS-11970
When using Collect Later/Never Services, the folders in the 'dataTransfer'
directory were not completely removed when the Service completed.

GS-12100
The 'EngineDestroySessionsOnLogoff' setting did not work.

GS-12102
Engines did not create the './work/&ltinstance>/tmp' directory at startup if it
did not exist. In 5.x versions, it did create the directory.


Stability,Fault Tolerance

GS-12180
Connectivity issues with the reporting database could cause the UI to become very unresponsive.