Intermittent message duplication for out or order multipart messages

[prashan-abey]

We have encountered an issue where Jasmin intermittently creates duplicate messages for multipart incoming messages. The message we tested had 3 out of order segments. Jasmin reassembled the message fine but intermittently we see Jasmin create a duplicate of the message and send it downstream.

We replicated this issue on both Jasmin 0.9.25 and 0.11.0 versions.

Message content tested:
'From also contains a display name (Alice) and a SIP or SIPS URI that indicate the originator of the request. This header field also has a tag parameter containing a random string that was added to the URI by the softphone. It is used for identification purposes.\n 1234567890 1234567890 1234567890 1234567890 1234567890'

message.log entries:

2024-09-13 10:43:57 INFO     19354 SMS-MO [cid:Pivotel] [queue-msgid:f1c868d8-b3c3-43ad-900c-cf56c628224a] [status:ESME_ROK] [prio:LEVEL_0] [validity:None] [from:61401265373] [to:61480094159] [content:'From also contains a display name (Alice) and a SIP or SIPS URI that indicate the originator of the request. This header field also has a tag parameter containing a random string that was added to the URI by the softphone.  It is used for identification purposes.\n 1234567890 1234567890 1234567890 1234567890 1234567890']

2024-09-13 10:43:57 INFO     19354 SMS-MO [cid:Pivotel] [queue-msgid:faea4c4e-d538-4719-af8f-8622bc6bdaa1] [status:ESME_ROK] [prio:LEVEL_0] [validity:None] [from:61401265373]

[Incoming_SMPPC.log](https://github.com/user-attachments/files/17093974/Incoming_SMPPC.log)

The issue is happening intermittently. While looking at the logs, it appears that for the messages that got duplicated, Jasmin handled multiple incoming transactions at the same time whereas for the messages that did not duplicate Jasmin processed inbound transactions sequentially. This could not be related but one of the patterns we picked up.

Is Jasmin supposed to process inbound transactions sequentially? Is there anything else that could contribute to this issue? 

This is the one that duplicated
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction started with message id 2008702790
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction finished with message id 2008702790
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction started with message id 2008702791
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction started with message id 2008702792
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction started with message id 2008702793
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction started with message id 2008702794
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction finished with message id 2008702792
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction finished with message id 2008702794
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction finished with message id 2008702791
2024-09-13 10:43:57 DEBUG    19354 Inbound transaction finished with message id 2008702793
2024-09-13 10:43:58 DEBUG    19354 Inbound transaction started with message id 2008702900


This is a sample of one that did not 
2024-09-13 09:10:25 DEBUG    19354 Inbound transaction started with message id 2007688737
2024-09-13 09:10:25 DEBUG    19354 Inbound transaction finished with message id 2007688737
2024-09-13 09:10:25 DEBUG    19354 Inbound transaction started with message id 2007688739
2024-09-13 09:10:25 DEBUG    19354 Inbound transaction finished with message id 2007688739
2024-09-13 09:10:46 DEBUG    19354 Inbound transaction started with message id 2007692879
2024-09-13 09:10:46 DEBUG    19354 Inbound transaction finished with message id 2007692879