Interaction Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- This release introduces the option max-database-request-queue-size in the [settings] section. It sets the maximum size for the database request queue. Any client request that generates a database request will be rejected if the current queue size reaches the specified maximum. The default value is 10,000 and the valid value is any integer in the range 5,000–200,000. Changes take effect immediately.
- There are two new KPI counters: current_request_queue_size and current_request_queue_wait. Like all other counters, these are accessible in ping messages, the health monitor, or datastream reporting. This feature relates to the resolved issue described below.
- A new configuration option in the [health-service] section controls whether and how often the current counters are written to the log file: log-output-timeout specifies the time, in seconds, between these log messages. The default value is 0 seconds (no logging), and the valid value is an integer in the range 1–600 (10 minutes). Changes take effect immediately. This feature also relates to the resolved issue described below.
This release contains the following resolved issues:
This release fixes an issue with the server exiting unexpectedly while trying to process corrupted XML messages that were captured by File Capture Point, or possibly by another capture point that handles XML messages. Such corrupted XML messages might be produced by custom transformation scripts. (ESR-12038)
This release fixes an issue, which existed on Linux platforms only, in which the processing of requests slowed down when the internal queue of requests grew. Previously the rate of processing depended on the queue size and in this release there is no dependency. The new KPI counters and the log-output-timeout option described above also relate to this resolved issue. (ESR-11934, ESR-11974)
This release fixes an issue with the server exiting unexpectedly, in some cases, when a connection of DB Server to an Oracle database was killed by Oracle administrative tools or scripts. (ESR-11823)
When Interaction Server switches over in a high-availability configuration at a time when there are outstanding requests from Orchestration Server to pull interactions for processing, Interaction Server terminates properly. Previously, it did not terminate properly in some instances of this scenario. (ESR-11435)
No special procedure is required to upgrade to release 220.127.116.11.