GridServer 6.1.0 Hotfix 02 is now available
Article ID: KB0104192
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Description:
Dear GridServer Users,
We just released HF-02 for GridServer 6.1.0.
Closed Issues in 6.1.0_hotfix02 (This Release)
Routing and Balancing
GS-11846
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 unnecessary backlogged balance messages.
GS-11892
The Engine message send timeout used for rebalance logoff messages (default
100ms) may be too short for some network configurations, such as when some
Engines are on a WAN. It can now be configured via 'Manager Configuration->Balance Message Timeout'.
Security
GS-11663
When using Kerberos authentication, if a browser window was left open for longer 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.
Dear GridServer Users,
We just released HF-02 for GridServer 6.1.0.
Closed Issues in 6.1.0_hotfix02 (This Release)
Routing and Balancing
GS-11846
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 unnecessary backlogged balance messages.
GS-11892
The Engine message send timeout used for rebalance logoff messages (default
100ms) may be too short for some network configurations, such as when some
Engines are on a WAN. It can now be configured via 'Manager Configuration->Balance Message Timeout'.
Security
GS-11663
When using Kerberos authentication, if a browser window was left open for longer 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.
Issue/Introduction
GridServer 6.1.0 Hotfix 02 is now available
Environment
Product: TIBCO DataSynapse GridServer
Version: 6.1.0
OS:
--------------------
Feedback
Yes
No
Powered by
