Re: [twitter-dev] firehose exception: "the end of stream has been reached"

Thanks for the responses. That's unfortunately not the case. We've gone massively concurrent with this (we've wrapped our own concurrent queueing around twitter4j, which it looks like Yusuke has just updated to add his own concurrent approach to this...thx), and falling behind on the stream is de

Re: [twitter-dev] firehose exception: "the end of stream has been reached"

Hey Dan, If you fall too far behind when receiving the stream we will disconnect you. Check the timestamp of the Tweets being received to the time on your computer. If the times are drifting further apart you are falling behind. The most common reasons for falling behind are: 1. You are attemptin

Re: [twitter-dev] firehose exception: "the end of stream has been reached"

Not seeing these issues, but I'm not using the firehose, so that probably explains it. However : * To avoid being rate limited, please read this document (and implement it, because reading the document won't solve it):

[twitter-dev] firehose exception: "the end of stream has been reached"

Our app is using twitter4j 2.1.9-SNAPSHOT against the twitter firehose, and lately we are having problems with the stream "just ending" out of the blue. It happens several times a day lately with no rhyme or reason. Here's an example of what we see: Stream closed.TwitterException{exceptionCode=[a