You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// With the gateway persistence seam v1 design it's only safe to deduplicate when there is a tx scope present since the check happens before
57
+
// the messages have been pushed to the transport. If we add entries earlier they would be considered duplicate when retrying after something went wrong.
58
+
// Note: The gateway will always wrap the v1 seam invocation in a transaction scope
// This implementation is not 100% consistent since there is a race condition here where another thread might consider the same message as a non-duplicate.
17
+
// We consider this good enough since this is the inmemory persister which will not be consistent when the endpoint is scaled out anyway.
//another thread might already have added the ID since we checked the last time
35
+
if(clientIdSet.ContainsKey(clientId))
36
+
{
37
+
// another thread has proceed this ID already and there is a potential duplicate message but there is nothing we can do about it at this stage so just return.
38
+
// Throwing would just cause unessessary retries for the client.
0 commit comments