Every hours in our Azure API logs we get Handled CometD Exception: 403::Unknown client

[p4rvr]

At the same time we see

Category: CometD.NetCore.Salesforce.ResilientStreamingClient
EventId: 0

System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.Net.CookieCollection.IndexOf(Cookie cookie)
at CometD.NetCore.Client.Transport.LongPollingTransport.GetResponseCallback(IAsyncResult asynchronousResult) in C:\projects\cometd-netcore\src\CometD.NetCore\Client\Transport\LongPollingTransport.cs:line 29

This occurs every hour in our logs and there are times where we stop seeing any platform events from Salesforce. Once we restart our Azure API APP which is running this code then we begin to see platform events published by Salesforce again.

Thoughts?

[xdansmith]

We're seeing same issue happen. It seems to be a known condition that happens with Salesforce and CometD - but I believe this library could be improved to handle this condition automatically? Did you ever figure out a solution to this?