Revision as of 23:52, November 7, 2016 by Olena (talk | contribs)
Jump to: navigation, search

Known Issues and Recommendations

Chat Server

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Chat 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 ChatServer.xml template file contains an error that blocks the import of metadata. To correct this error:

  1. Open ChatServer.xml in a text editor.
  2. Locate the line that includes "Debugging purposes only"
  3. Remove <b> and </b> from this line and save the file.
ID: ESR-12033 Found In: 8.5.105.05 Fixed In: 8.5.106.10

Enabling the ADDP protocol on the connection to Chat Server's webapi (flex-chat) port may cause the following Chat Server error when the connection is closed by a client based on Platform SDK for Java 8.5 (that is, GMS):

error: ConnTimerQueue.cpp:131 Invalid argument 'timeout >= 0' value

Genesys recommends that you not configure the ADDP protocol for Chat Server's webapi (flex-chat ) port. Due to the nature of short-lived connections with the flex protocol, ADDP does not provide any advantage.

ID: PSDK-8501 Found In: PSDK 8.5.000.10 Fixed In: See the note below

Note: ADDP support has been corrected not to send ADDP disabling Xoff(-1) packet when connection is being closed.


If Chat Server is switched from backup mode to primary mode, Chat Server will exit if inactivity control is enabled and the alert timer expires.

ID: ESR-11548 Found In: 8.5.102.08 Fixed In: 8.5.104.08


Internationalization Issues

Information in this section is included for international customers.


There are no internationalization issues for this product.


Comments or questions about this documentation? Contact us for support!