Only first messages are processed

[RadekDevaAs]

Hi,
Great work and amazing blog post!

I tried to run the sample just to see how it work in .NET. However, only the first few messages are getting processed. It is that due to the fact "INTERVAL_OPTION" is not set? I also do see that cometd has backoff property. I am just not sure how should I tackle this reconnecting. It is something supported out of the box or I just need to create a loop with wait and reconnect?

[sean-on]

I second the thank you, this project was a great headstart for some new work on my plate.

I ran into this issue as well;
it looks like there is a line in the LongPollingTransport (GetResponseCallback) that is intended to suppress timeout error messages, but it's also preventing the reconnect behavior from running.

the result is that once the first timeout occurs you stop receiving messages.

removing the condition alone is enough to get it running beyond the first timeout in my testing.

It wasn't clear to me what messages were intended to be suppressed (not seeing anything in the logs) otherwise I would have submitted a PR.

[ttjackott]

This stumped me for quite some time, thanks for raising this issue!

[brendan-nobadthing]

Thanks! I can confirm that commenting-out the error suppression worked for me too.

// end of LogPollingTransport.GetResponseCallback  
catch (Exception e)
            {
                // if (!e.Message.Contains("operation has timed out")) // Supress timeout messages due to inactivity
                   exchange.listener.onException(e, ObjectConverter.ToListOfIMessage(exchange.messages));
                exchange.Dispose();
            }