Known Issues and Recommendations
Social Messaging Server
The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Social 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 Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
See also: Internationalization Issues
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: 8.5.101.07||Fixed In:|
Social Messaging Server must have only one Interaction Server in its Connections. By design, Social Messaging Server does not support multiple Interaction Servers. Previously, Social Messaging Server activated connections to all Interaction Servers listed on its Connections tab, but it used only the first connection in the list.
|ID: SMD-1482||Found In: 8.1.400.05||Fixed In: 8.5.000.11|
Social Messaging Server does not support the "backup-port" option as a part of client-side port, because of a limitation in the Java PSDK. Social Messaging Server instead uses the value of the "port" option.
|ID: SMD-1440||Found In: 8.1.400.05||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: 8.1.201.06||Fixed In:|
Information in this section is included for international customers.
There are no internationalization issues for this product.