Genesys Rules System Rules Engine Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Memory Monitor—To solve a problem with handling of OutOfMemory errors, a Memory Monitor has been implemented in GRE. It is designed to periodically check GRE's memory usage, and set its operational state to "over threshold" if memory usage exceeds the configured threshold. The state is reset to back to "normal" if memory usage comes back below the threshold. It also provides an option ("adaptive" strategy) to automatically adjust the configured threshold if an out-of-memory error occurs before threshold is reached (for example, if the configured threshold was set too high). MORE DETAILS.
- GRE now initially shows status as Initializing until it has read and processed all rule packages and is ready to take execution requests. If there are a large number of rule packages, or very large rule packages, GRE can take several seconds or even a minute to be ready. Previously, LCA would show GRE status as Running but GRE's status.jsp would show an offline status. Now the two statuses are synchronized.
This release contains the following resolved issues:
Previously, when the Configuration Server connection was lost and then reconnected, a new connection to the LCA was created, but the old one was never destroyed. Now, when the Configuration Server connection is re-established, GRE re-uses the existing LCA connection. (GRS-2754)
No special procedure is required to upgrade to release 220.127.116.11.