8.5.108.16
Stat Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 01/31/18 | General | Unavailable | X | X | X | X |
Helpful Links
What's New
As of February 5, 2018 this release is no longer available as it did not function as expected. Release 8.5.108.17 corrects the issue that required the removal of 8.5.108.16. All resolved issues from the 8.5.108.16 release are included in the 8.5.108.17 release.
Resolved Issues
This release contains the following resolved issues:
Stat Server now gracefully handles connection failures in the following specific scenario:
- Stat Server is started with [statserver]/enable-java=yes.
- The JVM path specified in [java-config]/jvm-path is not valid.
- A client tries to establish a connection to the Stat Server host on port 21000.
Previously, Stat Server terminated unexpectedly in this scenario. (SS-7972)
Stat Server now correctly packs CurrentState for place-groups. Previously, failure to do so could cause unexpected termination of connected clients. (SS-7968)
After a Configuration Server failover, Stat Server no longer tries to register DNs before the configuration is fully read. Previously, because Stat Server might have started registering DNs before complete agent login information was available, DN or agent states for some DNs or agents were incorrect. (SS-7938)
Stat Server performance when there are large numbers of connected clients has been improved. Previously, when the number of connected clients exceeded 500, T-Server(s) closed the connection(s) to Stat Server with the reason too slow. (SS-7926)
In the 10070|STANDARD log message GCTI_SS_OVERLOAD_DETECT, Stat Server no longer reports main-thread CPU usage as exceeding 100%. Previously, if an overload was detected and main-thread CPU usage was adjusted, the log message reported the unadjusted value of more than 100%. (SS-7864)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.108.16.