Closed Issues in 5.1.3_hotfix03 (This Release)

.NET Specific

GS-12216
A 64-bit Windows installation running in 32-bit mode due to a Grid Library
marked as 'os=win32' could not run a .NET service. Note that a pure .NET Grid
Library typically should not have the os attribute set, since assemblies are not
specific to bitness.

C++ Specific

GS-12268
32-bit Windows C++ Services would fail to run on 64-bit Engine installations
when the Run-As user was set.

Database

GS-12083
Two new reporting database settings have been added: 'Maximum Task Description
Length' and 'Maximum Service Description Length'. These are used to truncate the
description lengths to the size of the database columns if attempts to store
values greater than the column size causes problems with the database.

Engine Daemon-Unix

GS-12092
A Manager upgraded from 5.1.2 was missing the files required to synchronize the
Unix Engine JRE's. This means that an Engine that migrated from a different Grid
with a different JRE version would continue to use its JRE. The files are
restored by this hotfix, but.if they already exist (for example, the JREs have
already been upgraded), they will not be clobbered.

Engine Daemon-Windows

GS-12184
Certain processors could show -1 as number of CPUs on Windows Daemons, and would
launch only one Engine by default.

Resource Deployment

GS-12235
Windows 32-bit Services would fail to run on a 64-bit Daemon installation under
the following circumstances: A Windows 32-bit JRE Grid Library with a newer
version was deployed, but not packaged in the same way as the default one
deployed with GridServer, even if that JRE is correctly packaged and works on
other Services. Such JRE Grid Libraries will now work with these 32-bit
services.

Security

GS-12248
A minor cross-site scripting vulnerability has been fixed. It does not exist in
modern browsers, and only under atypical circumstances, such as using Internet
Explorer 8 and setting the security level for the site to low. Also, it only
applies to a request that does not have a session. It has been fixed primarily
to avoid false positives on penetration tests.

GS-12256
The browser hint "autocomplete='off'" for the password field on the login page
can now be set. This is done on the Manager Configuration>Security page.

Stability,Fault Tolerance

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

GS-12225
On occasion a corrupt keypair was generated for the Driver to Manager
connection, resulting in the Manager creating a flood of log messages containing
'javax.crypto.BadPaddingException: Invalid pad value!’. The Driver will now log
itself off and back on to generate a new keypair if this situation arises. This
is a rare condition and has only been observed on Solaris.