GridServer 6.3.1 Hotfix2 has been released

GridServer 6.3.1 Hotfix2 has been released

book

Article ID: KB0101604

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer 6.3.1

Description

GridServer 6.3.1 Hotfix2 has been released. Here are the release notes:
================================================================================
Affected Components for 6.3.1_hotfix02
 
The following components are updated by this hotfix:
 
Engine
Manager
Scheduler
Tomcat
 
 
================================================================================
Closed Issues in 6.3.1_hotfix02 (This Release)
 
 
Engine
GS-14825
When the ssl.keystore and ssl.pem files are placed in the engineUpdate/shared
folder on the Broker, the Engine will no longer endlessly attempt to update
those files.
 
GS-15584
When a job is rescheduled, the job status change has been added to the logged
information. 
 
GS-15610
Fixed some typos and spelling errors in the Engine logs.
 
GS-16073
Fixed an issue where Engines would start picking up tasks before they had
completed Grid Library synchronization.
 
GS-16201
Fixed an issue where the Engine would hang after having the exception
"java.io.IOException: Could not find the Processing Instruction for this XML."
 
 
Manager
GS-15842
When creating a new Service Type, the resulting .gsdd schema file will now have
correct carriage return/newline whitespace according to the Manager platform.
 
GS-15911
When using Windows Authentication, the Driver could not log in due to the User
Role not being mapped during the Broker authentication and authorization. With
this fix, the User Role will be mapped once User is authenticated with the
Broker.
 
GS-16043
When using LDAP or Windows Authentication, a User needs to log in at least once
into a Standalone Director before being able to log in on a Standalone Broker.
This is because all the User information is stored inside the Standalone
Director. If a Windows User logs in to the Standalone Broker for the first time
without a prior login to the Standalone Director, the User will be informed to
log in to the Standalone Director at least once. If the User already exists in
the Standalone Director's user repository (internal database), the User could
log in to the Standalone Broker even if the Standalone Director is restarted.
 
GS-16254
When "Use HTTPS for Engine Communication” is true, the HTTPS protocol will be
used for data input/output.
 
 
Scheduler
GS-15665
Fixed a java.util.ConcurrentModificationException in the Scheduler.
 
 
Tomcat
GS-16219
Apache Tomcat has been updated to version 8.5.50.
 
GS-16289
Engine JRE has been updated to 1.8.0_241.
 
================================================================================

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

Issue/Introduction

GridServer 6.3.1 Hotfix2 has been released