Issues reported with Streams since 10/21

[andypiper]

So to clarify, you’re posting on this thread because you’re seeing a large number of short-term disconnections?

[vivienanglesio]

So after some investigation, the disconnections are due to the timer that disconnect the stream when there is no activity on the stream for more than 90sec like mentionned in your documentation : https://dev.twitter.com/streaming/overview/connecting

My timer is based on http level activity (the timer is reseted each time an http chunk is received from twitter’s server)

[vivienanglesio]

Yes i’m posting on this thread because i have a lot of disconnect/reconnect on my streams. My application is running since several years and i’m experiencing this kind of issue only since the 10/21. That’s why i’m posting here.

I hope it’s the good place

[andypiper]

Thanks for clarifying. We’ll keep this thread open for the overarching issue.

[talkingfrog1950]

Hi Andy

We are now getting 413 errors on our site streams connection attempts:

“Error 413: Parameter user_id has too many items specified”

We connect a single stream at a time to the site stream connection so it isn’t a matter of trying to initiate too many streams.

[phuc77]

Hi,

I’m also wondering about the “connection: close” header in the response when connecting to stream.twitter.com.
Shouldn’t this be keep-alive?

Using Apache httpclient 4.5.2, the request goes like this:
“http-outgoing-0 >> “POST /1.1/statuses/filter.json HTTP/1.1[\r][\n]””
“http-outgoing-0 >> “Authorization: OAuth oauth_consumer_key=”…”, oauth_nonce="…", oauth_signature="…", oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1477402380”, oauth_token="…", oauth_version=“1.0”[\r][\n]""
“http-outgoing-0 >> “Content-Length: 31[\r][\n]””
“http-outgoing-0 >> “Content-Type: application/x-www-form-urlencoded; charset=UTF-8[\r][\n]””
“http-outgoing-0 >> “Host: stream.twitter.com[\r][\n]””
“http-outgoing-0 >> “Connection: Keep-Alive[\r][\n]””
“http-outgoing-0 >> “[\r][\n]””
“http-outgoing-0 >> “track=trump&stall_warnings=true””

And in the response, I get:
“http-outgoing-0 << “HTTP/1.1 200 OK[\r][\n]””
“http-outgoing-0 << “connection: close[\r][\n]””
“http-outgoing-0 << “content-type: application/json[\r][\n]””
“http-outgoing-0 << “date: Tue, 25 Oct 2016 13:33:02 GMT[\r][\n]””
“http-outgoing-0 << “server: tsa[\r][\n]””
“http-outgoing-0 << “transfer-encoding: chunked[\r][\n]””
“http-outgoing-0 << “x-connection-hash: a9aab11f353f7410a61066ae9b4d0b82[\r][\n]””
“http-outgoing-0 << “[\r][\n]””

If I try to do the same using https://dev.twitter.com/rest/tools/console
the response is:
HTTP/1.1 200 OK
x-connection-hash: 981b94c1fb752a65e152faff3aeedb77
Date: Tue, 25 Oct 2016 13:41:00 GMT
Content-Length: 0
Connection: keep-alive
Content-Type: application/json
Server: tsa

So, why am I getting “connection: close” header?

[skruk]

I’m getting the very same responses.

[andypiper]

I’m getting the very same responses.

Can you be specific - the same HTP headers, or the 413 error reported? Need to be very clear to understand how this relates to what is being reported. Thank you!

[skruk]

I’m getting HTTP/1.1 200 OK followed by Connection: close, Server: tsa

[SidecastrPicks]

We are also are getting “close” in our response header :

New Connection Status: 200, Reason: OK Headers: {“CONNECTION”=>“close”, “CONTENT_TYPE”=>“application/json”, “DATE”=>“Tue, 25 Oct 2016 17:32:36 GMT”, “SERVER”=>“tsa”, “TRANSFER_ENCODING”=>“chunked”, “X_CONNECTION_HASH”=>“281d7650dd1eeb0b287a6e956b0553ab”}

[eliasisrael]

Andy –

Please, please tell me you are onto some fix. We’re 5 days into trying to resolve this and it’s holding up our ability to sell, costing us users, and preventing us doing a new feature release as well.

We’re in kind of a lot of pain here. Please tell me we’re going to see the light at the end of the tunnel?
Thanks.

Best,
Eli

[andypiper]

We are working on the issue. I understand that applications are affected and that this of course has effects on your services. Apologies for the disruption and I’ll share things here as and when I have news.

[SidecastrPicks]

Hello Andy,

We have been running Twitter streaming client ing AWS - US- East region for almost 4/5 years. Until thrusday everything was running fine. Since Friday, our client script connects to Twitter and only gets 0 to 4 tweets, then goes to slience. No warning / disconnect messages and neither the socket closes. Script runs forever but no Tweets at all. As I mentioned in pervious post, we do get response from our connections with “Close” in header. Not sure that is affecting the stream or not.

New Connection Status: 200, Reason: OK Headers: {“CONNECTION”=>“close”, “CONTENT_TYPE”=>“application/json”, “DATE”=>“Tue, 25 Oct 2016 17:32:36 GMT”, “SERVER”=>“tsa”, “TRANSFER_ENCODING”=>“chunked”, “X_CONNECTION_HASH”=>“281d7650dd1eeb0b287a6e956b0553ab”}

We then started our client in AWS-US-West region, and our client works perfectly. We get normal tweet stream without any problem. Though we get same response back from connection request

New Connection Status: 200, Reason: OK Headers: {“CONNECTION”=>“close”, “CONTENT_TYPE”=>“application/json”, “DATE”=>“Tue, 25 Oct 2016 17:53:26 GMT”, “SERVER”=>“tsa”, “TRANSFER_ENCODING”=>“chunked”, “X_CONNECTION_HASH”=>“c6f73e4eee93cd48c62f50eaea740d69”}

Thanks,
Sidecastr Team

[andypiper]

Thank you for the information, I’ll make sure the team working on this sees these additional data points as they continue to investigate and work towards a resolution.

[mulka]

Still seeing the connection being closed a few seconds after it is established.

[eliasisrael]

Hi Andy –

We’re now seeing MUCH more normal connection behavior. Thank you for staying on top of this, I do think we’re seeing the light at the end of the tunnel. Great work; keeping our fingers crossed while we watch things catch back up.

Best,
Eli

[andypiper]

The engineering and backend teams believe that these specific issues have now been resolved. Please let us know if the issues that sparked this thread remain a problem. To avoid confusion, I’ll shut this thread off shortly to avoid unrelated “me too!” discussions

While the public streaming API endpoints remain open and free to use, as with the rest of the public API endpoints, we can only suggest that the API is available on a best efforts and unsupported basis.

That said, we’d also like to remind consumers particularly of streaming / realtime data that fully-supported products are available via Twitter’s Gnip data team. Thanks!

[johndburger]

For what it’s worth, I can report that my connection issues appear to have gone away as of about 18:40 UTC. Thanks!

[mulka]

Looks like the problems have gone away from my point of view.

[andypiper]