GridServer 6.3.1 Hotfix6 has been released. Here are the release notes:
================================================================================
Affected Components for 6.3.1_hotfix06

The following components are updated by this hotfix:

.NET Specific
C++ Specific
Communication and Network
Database
Documentation
Drivers-All
Engine
Engine Daemon
Java Specific
Manager
Security
Services
Tomcat

================================================================================
Closed Issues in 6.3.1_hotfix06 (This Release)

.NET Specific
GS-17280
Sometimes, the Engine throws a System.Runtime.Remoting.RemotingException from .NET Remoting when you use Non-Uniform Memory Access (NUMA) CPU configuration.


C++ Specific
GS-17504
All the Linux driver libraries are now compiled with the SONAME attribute.

GS-17694
Support for gcc83 compiler has been added.


Communication and Network
GS-16556
If the value of the NAT Translation Range field is set to zero (0.0.0.0/0) and the value of the Translate Inside Range field is set to False, then the Engine is unable to log in to the Broker.


Database
GS-17940
You can now encrypt or decrypt the Internal.script, Internal database, and Reporting database passwords present in the installation.properties file.

Considerations for Enabling Encryption:
> For the Internal.script file: This change is only for Primary Director and Secondary Director because there is no separate internal database for Brokers. If you set the property to true on the Primary Director and false on the Secondary Director, the Internal.script file on the Secondary Director becomes unreadable. This happens because the Secondary Director backs up the database from the Primary Director.
> For Grid Deployment with different hotfixes: In case the property is set to true, components on the lower versions (6.3.1-hotfix05 and lower) are not supported. Ensure that all components use GridServer Manager version 6.3.1-hotfix06.

To enable or disable encryption (GUI Installation Mode)
1. Install or upgrade the server as required.
2. Go to the DS_DATA\conf folder and open the installation.properties file for editing.
3. In the installation.properties file, set the DSPasswordEncryption property to true (to enable encryption) or false (to disable encryption) as required.
4. Reinstall the server from Admin > Manager Reinstall.

To enable or disable encryption (Silent Installation Mode)
1. Go to the DS_MANAGER folder and open the install.silent file for editing.
2. In the install.silent file, set the passwordEncryption property value to true (to enable encryption) or false (to disable encryption) as required.
3. Install or upgrade the server as required.

To change the property later, perform the steps mentioned below:
GUI Installation Mode
1. Edit the installation.properties file under DS_DATA\conf.
2. Set the DSPasswordEncryption property to true or false.
3. Reinstall the server through Admin > Manager Reinstall.

Silent Installation Mode
1. Edit the install.silent file present under DS_MANAGER.
2. Set the passwordEncryption property value to true or false.
3. Provide the managerId in the install.silent file and re-install the server. (You can find the managerId in the installation.properties file present under DS_DATA\conf).


Documentation
GS-14180
The build version value is now mentioned in the 6.3.1-hotfix06 readme file.


Drivers-All
GS-16948
Although you should not be able to transfer the task data in a Driver session over Direct Data Transfer to other sessions, you are able to do so.


Engine
GS-16847
On the Engine > Daemon Admin and Engine > Engine Admin page, for Windows Server 2019, the value of the OS Name field is displayed as "Unknown".


Engine Daemon
GS-17566
When a 64-bit Engine crashes, it attempts to restart as a 32-bit Engine and goes into a loop.


Java Specific
GS-16550
Azul Java 8 and Azul Java 11 are now supported by GridServer Manager version 6.3.1.
Azul Java 11 support is not provided for Solaris OS.

Perform the following steps to create a custom Engine JRE:
1. Shut down all the running Engine Daemons.
2. Download the new required JDK version.
3. Create a temporary directory. For example, temp.
4. Copy the new JRE from JDK to the temporary directory. In the case of Java 11, copy JDK to the temporary directory.
5. For Unix, rename the temp folder to jre.platform. For example, jre.linux-amd64. For Windows, rename temp folder to jre.
6. Create tar.gz for Linux or zip for Windows archive of the directory containing the renamed folder. For example, jre.linux-amd64.tar.gz or jre.win-amd64.zip.
7. Go to $DS_INSTALL/manager/webapps/livecluster/public_html/register/install/jre/.
8. Remove the tar.gz or zip file that you want to replace.
9. Now, copy the newly created tar.gz or zip file to $DS_INSTALL/manager/webapps/livecluster/public_html/register/install/jre/.
10. For Unix, change the permission of the newly copied tar.gz file to 775. For example, chmod 775 jre.linux-amd64.tar.gz. No action needs to be performed for Windows.
11. Edit the jre.platform.dat file. For example, jre.linux64.dat or jre.win64.dat.
12. Replace the version number of the old JRE version with the new JRE version.
13. Start the engines again.

GS-16328
Added Oracle JDK and OpenJDK Java 11 support for GridServer Manager version 6.3.1.
> A new version of Engine JRE created by using Oracle JDK 11 is available. By default, Engine JRE is Oracle JAVA 11 for Win64 and Linux64.
> Grid library has been added to run the Engine on Oracle Java 1.8.0.311 for Windows and Linux.
> Java 11 support is not provided for Solaris OS .

Note for Linux64 Engine:
Prior to moving Engines from any version earlier than 7.0.0_hotfix08 to 6.3.1_hotfix06, you must perform the following steps:
1. Stop the server.
2. As a best practice, take a backup of the existing engine.sh file.
3. Replace engine.sh file from the engineScriptUpdate folder to datasynapse/manager/webapps/livecluster/engineUpdate/linux64/ and datasynapse/manager-data/engineUpdate/linux64/ folder.
4. Start the server.
5. Let the Engines log in and then restart the Engine Daemon.
6. Move the Engines.

In case of Grid Architecture, perform steps 1 to 5 on the Primary Director.

To upgrade from all versions, you must perform the following steps:
1. Stop the server.
2. As a best practice, take a backup of the existing engine.sh file.
3. Replace the engine.sh file from the engineScriptUpdate folder to datasynapse/manager/webapps/livecluster/engineUpdate/linux64/ and datasynapse/manager-data/engineUpdate/linux64/ folder.
4. Start the server.
5. Let the Engines log in and then restart the Engine Daemon.
6. Stop the server.
7. Upgrade the server.

In the case of upgrade, perform steps 1 to 7 on the Primary Director.

GS-17941
The Engine JRE has been updated to Java version 1.8.0_351.


Manager
GS-17385
When Direct Data Transfer is disabled and the Invocation Per message is set to greater than 1, tasks might appear to be missing on the Broker.

To fix this issue, go to the configuration: Admin > Manager Configuration > Hotfixes > GS-17385 and set it to True.

GS-17456
You can now add Engines to the Grid when the Primary Director is down.

To enable the installation of the Linux Engine on the Secondary Director, the -d parameter is added.

-s primarydirector:port -d secondarydirector:port

GS-17936
A new configuration property, Reschedule Task, has been added to Engine Configuration. This property allows rescheduling the tasks when a memory cap is detected.
In case of an upgrade from any hotfix between 6.3.1_hotfix01 to 6.3.1_hotfix05, this property needs to be added manually.
Make the following changes in the Config.xml.unix for Linux and Config.xml.win32 for Windows available under DS_DATA\conf:
> Add the following attribute under the <PROPERTIES> tag: RESCHEDULE_MEM_EXCEED="true"
> Add the following property name under the <TYPES> tag: <PROPERTY NAME="RESCHEDULE_MEM_EXCEED" TYPE="boolean"/>

GS-17724
Logging has been added for clarity when certain actions are attempted with a task that is already completed.


Security
GS-16864
The jQuery library has been updated to version 3.6.0.


Services
GS-17937
An option has been added to disable Service Priority 10 at the Manager level.

This option is available at Manager Configuration > Services > Scheduling > Enable Preemption for Urgent Job.


Tomcat
GS-17944
Apache Tomcat has been updated to version 8.5.87.

================================================================================
To download this hotfix, login to the Support Portal and navigate to Downloads > Hotfixes > AvailableDownloads > DataSynapse > GridServer > 6.3.1.