Duplicate messages

Error Description

Customers are experiencing duplicate feed messages, particularly evident during sequences of messages rather than isolated occurrences.

Definition: A message can be deemed duplicate if it has the same timestamp, event ID and message type.

Applies to

UOF SDK Java (v3.0.0) or older

Please note that the fix is delivered in Java SDK v3.1.0.

Symptoms

When the Rabbit connection remains disconnected for more than 180 seconds, the SDK attempts to restart the current channel and create a new one. Original channels may not be completely closed, leading to duplicate messages arriving via both channels. Subsequent disconnections may create additional channels, exacerbating the issue.

Processing multiple messages from different channels out of order requires additional network and CPU resources on the user's side.

Resolution

We recommend upgrading your Java SDK to v3.1.0

Customers who are using Java SDK v3.0.0 -

The only current workaround is for the user to restart the SDK instance. To mitigate long message recovery periods after restart, preserve the message recovery timestamp before shutting down the old SDK instance and set it before opening the feed on the new SDK instance.