Jump to: navigation, search

Known Issues and Recommendations

Interaction Server

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Interaction Server. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.

See also Internationalization Issues.

The statement of support for Red Hat Enterprise Linux (RHEL) 7 is missing from the read_me.html and ip_description.xml files in the installation package.

ID: ESR-11732 Found In: Fixed In:

The Web Service Capture Point does not work on Linux hosts when the number of open client connections is close to or exceeding 1024. On other platforms the limit is set by the OS-level limit of open files for the user (see, for example, the UNIX command "ulimit").

As a workaround, use Interaction Server Proxy as a middleman between Interaction Server and Agent desktop applications.

ID: ESR-8382 Found In: Fixed In:

When a client sends RequestStopProcessing to Interaction Server while the Interaction Server database is unavailable, Interaction Server does not send a request to delete this interaction from the database after the database becomes available again. At the same time in this situation Interaction Server sends EventAck to the client.

ID: ESR-8208 Found In: Fixed In: 

If DB Server disconnects just when a database transaction is about to start, there is the rare possibility that this particular interaction may became unreachable for further requests.

ID: ESR-8185 Found In: Fixed In:

When an interaction is placed in the workbin, Interaction Server sends the event EventWorkbinContentChanged before this change is saved in the database.

ID: IXN-4556, IXN-4609 Found In: Fixed In: 8.5.301.08

The routing-related health counters that were introduced in the release are available via ping events and REST web interfaces, but not via webservice/SOAP requests.

ID: IXN-4023 Found In: Fixed In: 

On non-Windows platforms, the Web Service Capture Point works correctly only if you use UTF-8 as the codepage for Interaction Server. If you use any other codepage, the data received from the Web Service Capture Point might be corrupted.

ID: IXN-3317, ESR-13023 Found In: Fixed In: 

Internationalization Issues

Information in this section is included for international customers.

There are no internationalization issues for this product.

This page was last modified on March 13, 2019, at 10:24.


Comment on this article:

blog comments powered by Disqus