Publishers cannot send to Unified API clients via Messaging

When a publisher sends a message to a Unified API client, the messages are not routed to the client's Messaging feature as expected but instead are delivered as if they were updates via topic streams.

Messages sent in this way do not have headers. If the messages are set as requiring acknowledgment, they are not acknowledged and cause a nack callback even though they have been delivered to the correct client, though through the wrong mechanism.

JMS adapter can duplicate messages received from Diffusion at configuration change

During configuration change there is a window during which both old and new JMS connections are in place and can deliver messaging from Diffusion clients to JMS destinations. A message sent from a Diffusion client to a topic associated with a JMS destination that is unaffected by a configuration change (i.e. it is neither removed or added) during the configuration change window is duplicated.

Latest value not notified for Record topics when new TopicStream added

If the Topics feature is used to add a new TopicStream that covers Record topics that are already subscribed to then the stream will be notified of subscription to the topic but will not be given the latest value for the topic and therefore would be unable to process subsequent deltas. For this reason, when using Record topics, it is important that the stream that will process the topics is added before the topics are subscribed to.

Issues with message loss on reconnect for Classic API clients and any clients using DPT

After reconnecting a C Unified API client to the same server it is possible that there could be some message loss. When using single value topics this may not be a problem as a full value is always delivered but for topics that deliver deltas this could mean that deltas are missed and therefore the current state is unknown. For this reason it is not recommended to use reconnection with C Unified API clients.

This issue will not be resolved. We recommend you do not use the DPT transport if you have reconnection configured. We recommend you use Unified API clients instead of Classic API clients.