|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
Default Value: 1024
Valid Values: 1024-65535
Changes Take Effect: After restart of Interaction Server
Specifies, in bytes, the amount of data to be read from a BLOB in each iteration.
Known Issues and Recommendations
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: 8.5.107.06||Fixed In: 8.5.108.05|
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: 8.5.000.10||Fixed In: 126.96.36.199|
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: 8.5.000.10||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: 8.5.000.05||Fixed In: 188.8.131.52|
Interaction Server, in rare cases, hangs in a heavy-loaded environment when StatServer connects to it.
|ID: IXN-4798||Found In: 8.5.302.12||Fixed In: 8.5.304.06|
Interaction Server does not handle fast reconnection of URS. In rare cases, one of the following occurs:
- URS disconnected from Interaction Server, and Interaction Server had to be restarted to restore service.
- Interaction Server did not send interactions to URS for routing.
|ID: IXN-4758, IXN-4718||Found In: 184.108.40.206, 8.5.201.05||Fixed In: 8.5.304.06|
If an interaction's binary data size is a multiple of the
option value, Interaction Server does not process any operations related to the interaction, including routing, handling by an agent, or viewing of its information. This error appears in the log as follows:
Dbg 27140 No record selected by statement or record does not exist (connection ID: 1) Std 27013 ODBC error: (connection ID: 1, RC:0, CODE:0, SQLSTATE:'') ''
Workaround: Set a larger value for the blob-chunk-size option.
|ID: IXN-4708||Found In: 8.5.302.12||Fixed In: 8.5.303.08|
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: 8.5.108.06||Fixed In: 8.5.301.08|
Interactions submitted to Interaction Server via the integrated web service capture point in native (non-IWD) mode are always processed by Interaction Server with the attributes IsOnline and Hold that have the value of true or 1 regardless of the passed client attributes.
|ID: IXN-4442||Found In: 8.5.201.05||Fixed In: 8.5.302.12|
The routing-related health counters that were introduced in the 8.5.201.05 release are available via ping events and REST web interfaces, but not via webservice/SOAP requests.
|ID: IXN-4023||Found In: 8.5.201.05||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: 8.5.000.10||Fixed In:|
Information in this section is included for international customers.
There are no internationalization issues for this product.