Jump to: navigation, search

Known Issues and Recommendations

Digital Messaging Server

The Known Issues and Recommendations section is a cumulative list for all 9.1.x releases of Digital Messaging 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 .

During installation of DMS, the Select JDK/OpenJDK from list option on the Select Java Home screen is not displayed. Even if the option is displayed, Java 17 is not shown in the list.

Workaround: Use the Browse JDK/OpenJDK location option on the Select Java Home screen to select Java.

ID: DMS-903 Found In: Fixed In: 

If DMS is unable to restore active chat sessions during switchover after several attempts, a corresponding log message appears in the DMS log:

Std 42758 unable to restore chat sessions, Interaction Server is unavailable too long! Fixing connection to Interaction Server AND restarting DMS are strongly recommended to avoid potential data loss in active chat sessions.
ID: DMS-870 Found In: Fixed In: 

DMS does not support the Scalability mode of Genesys Driver for use with Genesys Hub.

ID: DMS-839 Found In: Fixed In: 

DMS fails to merge Twitter direct messages as the merge requests are not sent to Interaction Server.

ID: MSGA-2542 Found In: Fixed In:

DMS fails to restore chat sessions when chat clients, such as chat bots, leave a session without providing a reason.

ID: DMS-548 Found In: Fixed In:

You cannot immediately restart Digital Messaging Server after it has stopped. You must wait at least three minutes before starting Digital Messaging Server again.

ID: DMS-96 Found In: Fixed In:

The ESP strategy object in the sample Business Processes uses an outdated type of server: 3rd party server. It must be replaced with the SM Server type.

ID: SMD-2104 Found In: Fixed In: 

Social Messaging Server may receive an ESP request when the corresponding drivers are not ready to execute it, and thus a consistent response to ESP requests is not guaranteed.

ID: SMD-1062 Found In: Fixed In: 

In the DigitalMessagingServer.xml file, the [Log] messagefile default value is empty, but the value should be dmserver.lms, as in the template.

ID: DMS-69 Found In: 9.000.07 Fixed In:

Digital Messaging Server may show the wrong status in the following cases:

  • If the driver-classname or inbound-route option is set to an invalid value, the server shows its status as Service Unavailable.
  • If the value of any of the other options is changed, the Server shows its status as Started.
ID: DMS-65 Found In: 9.000.07 Fixed In:

Internationalization Issues

Information in this section is included for international customers. Release numbers in the Found In and Fixed In fields refer to the English (US) release of Digital Messaging Server unless otherwise noted in the issue description.

There are no internationalization issues for this product.

This page was last edited on October 6, 2023, at 09:46.
Comments or questions about this documentation? Contact us for support!