Duplication on the source

The source application has few options when providing the Message ID.

The Message IDs of received messages can look like one of these cases:

  1. Source application sends duplicated message, each with unique source Message Id.
    • SourceId1:-ION-:9436bbea68a54aad941eb532a5dbf5b0
    • SourceId2:-ION-:39db2b1127ae421caa56e5bd2779fbe5

    Duplication on the source cannot be identified by Message Id.

  2. Source application sends unique messages with duplicated source Message Id
    • SourceId1:-ION-:9436bbea68a54aad941eb532a5dbf5b0
    • SourceId1:-ION-:39db2b1127ae421caa56e5bd2779fbe5b

    This should not be happening in production, if yes, it is considered as a defect.

  3. Source application sends duplicated message with duplicated source Message Id
    • SourceId1:-ION-:9436bbea68a54aad941eb532a5dbf5b0
    • SourceId1:-ION-:39db2b1127ae421caa56e5bd2779fbe5

    If you can exclude the option 2, the duplication on the source can be identified by checking the source part of Message Id.

  4. Source application sends single message, which is duplicated during transfer
    • SourceId1:-ION-:9436bbea68a54aad941eb532a5dbf5b0
    • SourceId1:-ION-:39db2b1127ae421caa56e5bd2779fbe5

    If you can exclude option 2, the duplication on the source can be identified by checking source part of Message Id.

  5. Duplicated message is received without providing a message Id, can be any from the four previous options.
    • 9436bbea68a54aad941eb532a5dbf5b0
    • 39db2b1127ae421caa56e5bd2779fbe5

    Duplication cannot be identified.