9.0.016.11
Interaction Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 09/27/24 | Update | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Interaction Server’s JMS Capture Point now sends notifications for the same interaction in the correct order when it works on multiple notification threads mode. Previously in this scenario, the event notifications were sent in an incorrect order. (IXN-7932)
- Interaction server can now log reporting events with JMS Event Logger using multiple threads or JMS sessions. This improves the throughput of JMS Event Logger and prevents events flushing in case of Interaction Server’s internal message queue overflow. Additionally, it ensures that events for the same interaction are delivered in the correct order. (IXN-7940)
- Users can now monitor the number of JMS Capture Point’s notifications that are placed in the internal interaction queue and sent to JMS, and the current internal queue length by threads. (IXN-7967)
- Users can now monitor the number of JMS Event Logger’s notifications that are placed in the internal interaction queue, sent to JMS, and discarded due to queue overflow by threads. (IXN-7968)
Resolved Issues
This release contains the following resolved issues:
Interaction Server no longer shuts down unexpectedly when parsing request on health port. Previously in some cases, Interaction Server terminated on HTTP request with parameters. (IXN-7935)
Interaction Server has a fixed set of invalid request’s return database statuses, which are detected as database disconnects. If a customer’s database or ODBC driver generates a specific status, which is detected by Interaction Server as an error, but the invalid database request must be repeated, such status can be redefined as a disconnect using the setting settings/sql-disconnect-statuses. (IXN-7890)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.016.11.