session-expiration-timeout
Section: ha
Default Value: 120
Valid Values: 1 - 3600
Changes Take Effect: Immediately
Introduced: 8.5.109
Specifies, in seconds, how often the session expiration is checked during the time configured in the session-expiration-period option.
session-expiration-period
Section: ha
Default Value: 1800
Valid Values: 0 - 86400
Changes Take Effect: Immediately
Introduced: 8.5.109
Sets the session expiration period, in seconds. When the primary and backup Stat Servers, operating in high availability (HA) mode, cannot reconnect in time specified by the value of this option, the new session with the full statistics replication is initialized. When this option is set to 0 (zero), the lost session expires immediately.
connect-timeout
Section: ha
Default Value: 2
Valid Values: 1 - 3600
Changes Take Effect: Immediately
Introduced: 8.5.109
Timeout, in seconds, when the reconnect attempt between Stat Servers, operating in high availability (HA) mode, is made.
chunk-timeout
Section: ha
Default Value: 1
Valid Values: 1 - 3600
Changes Take Effect: Immediately
Introduced: 8.5.109
Duration, in seconds, between adjacent chunks during replication of statistics between primary and backup Stat Server instances. Term "chunk" means the number of statistics, processed simultaneously.
chunk-size
Section: ha
Default Value: 5000
Valid Values: 1 - 100000
Changes Take Effect: Immediately
Introduced: 8.5.109
Sets the number of statistics, processed simultaneously during replication of statistics between primary and backup Stat Server instances.
addp-trace
Section: ha
Default Value: both
Valid Values: local, remote, both, off
Changes Take Effect: Immediately
Introduced: 8.5.109
If addp is specified for the HA connection, the addp-trace option determines whether ADDP messages are written to the primary and backup Stat Server logs:
- local ADDP trace occurs on the side of the Stat Server in backup mode.
- remote ADDP trace occurs on the side of the Stat Server in primary mode.
- both ADDP trace occurs at both the primary and backup Stat Servers.
- off Turns ADDP off.
addp-timeout
Section: ha
Default Value: 10
Valid Values: 1 - 3600
Changes Take Effect: Immediately
Introduced: 8.5.109
If addp is specified for the HA connection, the addp-timeout option specifies the time interval, in seconds, that Stat Server in backup mode waits before polling the other Stat Server in the redundant pair.
addp-remote-timeout
Section: ha
Default Value: 10
Valid Values: 1 - 3600
Changes Take Effect: Immediately
Introduced: 8.5.109
If addp is specified for the HA connection, the addp-remote-timeout option specifies the time interval, in seconds, that Stat Server in backup mode instructs the other Stat Server in the redundant pair to use when polling to check the connection between the two servers.
8.5.109.19
Stat Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 05/07/18 | General | X | X | X | X |
Helpful Links
What's New
This release contains the following new features and enhancements:
- In addition to Warm Standby, Stat Server supports the Hot Standby redundancy mode for Stat Server high availability (HA) pairs on Windows and Linux platforms. See Hot Standby for more information.
- The following new configuration options, configured in the new [ha] section, have been added to support Hot Standby redundancy:
- Stat Server now recognizes the error code TERR_UNSUP_OPER(501) in EventError, received from SIP Server upon TQueryAddress on a routing point.
- New LMS messages are introduced:
- 10080|STANDARD|GCTI_SS_STAT_INVALID_FILTER|Invalid filter: '<name>' = '<value>'
- 10081|STANDARD|GCTI_SS_STAT_INVALID_TIME_RANGE|Invalid time-range: '<name>' = 'value'.
- Stat Server maps the content of the attribute_reason_desc from Interaction Server events to the value of the ReasonValue key in a UserData key-value list on an Action for the CurrentState or in a Reasons key-value list for the CurrentStateReasons. See CurrentState Categories for more information.
Resolved Issues
This release contains the following resolved issues:
Stat Server no longer terminates unexpectedly while writing the StatFile in the case when there is a connected PSDK client with an unspecified name. (SS-8196)
Stat Server no longer terminates unexpectedly on a tenant deletion. Previously, Stat Server terminated unexpectedly on the tenant deletion if there were duplicate routing strategy objects in Configuration Server. (SS-8168)
Stat Server now correctly calculates statistics of categories CurrentAverageTime/CurrentMinTime, when used with non-empty GroupBy and OrderBy specifiers. (SS-8159)
Stat Server now correctly calculates the following statistic on the SinceLogin aggregation interval:
Category=Formula
Objects=Agent,GroupAgents
Expression=SUM(LoggedOut;duration)
Subject=AgentStatus
(SS-8142)
Stat Server now correctly reports DN status start time in the CurrentState statistics. (SS-8084)
Stat Server no longer ignores the Selection time profile, when supplied with an old API statistical request. (SS-8061)
Stat Server no longer stops writing into a StatFile after Configuration Server failover. (SS-8046)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.109.19.