GridServer 6.1.1 Hotfix 2 is now available

GridServer 6.1.1 Hotfix 2 is now available

book

Article ID: KB0104871

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer -
Not Applicable -

Description

Description:
Dear GridServer Users,

We just released HF-2 for GridServer 6.1.1.

Closed Issues in 6.1.1_hotfix02 (This Release)

.NET Specific

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


Admin Interface

GS-11881
BrokerAdmin.addServiceDiscriminator() failed with the exception message "Can't
serialize null reference to DiscriminatorConditionSet Object"

GS-11977
When using LDAP, and the primary server is down, the User Admin table is empty.


Communication and Network

GS-11968
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.

GS-12066
The LDAP search timeouts did not always work. This is because, while the socket
connect timeout was set, the read timeout was not. The read timeout is now set
to the same value as the connect timeout.


Diagnostics

GS-11854
HTTP threads can now include the IP address and client information in the name.
This is useful when generating thread dumps for troubleshooting network
problems. To enable this, use the Manager Configuration&gtLogging setting 'Set the
Message Thread Names'. This takes effect immediately. Note that you should only
enable this when troubleshooting, as it can have a performance impact.

GS-12097
When an Engine was running a Task and was routed to antoher Broker after that
task completed, the message 'SEVERE: [Engine] while processing event...' was
logged with a stack trace. No actual severe event occured.


Engine Daemon

GS-12131
If a Daemon was installed using HTTPS, and SSL was configured using a PEM file
rather than having the machine trust the Manager's certificate, JRE
synchronization would fail. Note that a production environment should be
configured with the Manager's certificate in the chain of trust for any machine
that connects to it.


Engine Daemon-Windows

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


GUI

GS-11880
A number of controls did not work on Internet Explorer 10, such as the gears
icon used to pull down the Actions Menu.

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


Optimizations

GS-11976
When using Java and .NET Drivers, the thread that called the Task output handler
maintained a reference to the last output data object. This could cause problems
if the output data size was large. It is now nulled.


Routing and Balancing

GS-12005
User-defined Driver routing properties can now be changed at runtime, for the
sake of rerouting to Brokers based on rules without having to restart. For
example, the property 'color=blue' may be set at startup. The property can then
be set to 'green' via DriverManager.setProperty(). The next time the Driver logs
off and attempts a new login, such as by calling DriverManager.connect(null),
the Driver will be routed using the new property. Note that if the Driver has
Services running, it will remain on the same Broker, as this takes precedence
over routing properties.

GS-12117
When using the Weight Based Engine Balancer, it was possible for the Engines to
not be distributed properly according to weight


Security

GS-11883
The openssl libraries have been upgraded to 1.0.1e.

GS-12048
When using Kerberos authentication, if a browser window was left open for longer
than than the authentication token duration (10 hours default), clicking a link
on that page resulted in an error page indicating that the token had expired.
Forcibly refreshing the page resolved this by refreshing the token. The token is
now refreshed automatically and the page functions normally.


Server

GS-12088
An upgrade from 6.1.0_hotfix01 to 6.1.1 resulted in a nonfunctional Manager due
to a library collision.


Services

GS-12025
If a Task was resubmitted due to an issue downloading the output from a Daemon,
and the state had changed since the Task was submitted, the Task executed with
the resubmit state rather than the original submit state. It now uses the
original state.

GS-12095
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.

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


Stability,Fault Tolerance

GS-11885
It was possible for a Broker to become slow or unresponsive if sending rebalance
logoff notifications to Engines was taking longer than usual. This has been
fixed by removing unnecessary locking and discarding unecessary backlogged
balance messages.

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

Issue/Introduction

GridServer 6.1.1 Hotfix 2 is now available

Environment

Product: TIBCO DataSynapse GridServer Version: 6.1.1 OS: --------------------