Jump to: navigation, search

Known Issues and Recommendations

Digital Messaging Server

The Known Issues and Recommendations section is a cumulative list for all 9.0.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.

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: 

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: 

The DigitalMessagingServer.apd template does not specify values for the following options in the channel-any_name configuration section:

  • ucs-in-use
  • reconnection-timeout
  • ucs-request-timeout

The application uses the default values described in the Digital Messaging Server/Social Messaging Server Configuration Options Reference.

ID: DMS-66 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: 

The x-media-type-chat option must have the value wechatsession. Otherwise Digital Messaging Server cyclically reconnects to Chat Server.

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

The configuration option settings.subject-size must use values between 10 and 80.

ID: MSGA-867 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: 

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 September 26, 2018, at 15:40.
blog comments powered by Disqus