New Post: Events stop firing

As a followup to the above problem

Calling
stopstream
startstream

on the filter stream in the timer thread is fine if you are not receiving matching tweets at the time.

If you are receiving matching tweets at the time, the effect is that an extra Stopstream is generated After the start stream. i.e. you will see the events firing like this :

StopStream
StartStream
StopStream

Which means the attempt to recycle (during data) leaves the collection stalled - which is ironic as this is what we are trying to avoid by recycling the connection.

I dont know where the second StopStream is coming from, it has no call stack when observed in the debugger which suggests it is being called from the TweetInvi library perhaps ?

It is not being called from the MatchingTweet event as I have removed all calls to StopStream except the one in the timer.

This is nasty, I may have to try and pause the stream first and then delay before stopping and starting it. Either way it is not nice.

I would really appreciate some input on this as this problem has been open for some weeks now.