Hi Linvi,
I have a program that polls the Twitter REST API for a number of Twitter Users.
I've been getting the following occasionally:
--- Date : 13/04/2015 14:21:48
URL : https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=JeremyClarkson&include_rts=True&exclude_replies=False&contributor_details=False&count=200&trim_user=False&include_entities=True
Code : 408
Error documentation description : Twitter was not able to perform your query within the Timeout limit of 10000 ms.
The program would run without error for some time (up to a week) and then queries would start timing out. Once one had timed out, more & more will time out until no queries are returning within 10s.
Restarting the program fixes the problem. You can even leave the broken instance still running and start a new instance of the program which will work fine.
I don't believe this to be network related as I have reproduced the error on a Windows Azure instance (which is completely separate from our own hardware that we usually run the application on).
I don't think the queries are even being sent to Twitter because when I leave TCPView open, once the timeouts are happening for all requests, the packet counts & sent and received bytes for each open connection doesn't change.
Up until the end of last week I was running it with about 5 users, but it now has about 40 users. Since I have added the additional users, these errors have started happening far more frequently. Now I'm lucky if it works for 5 minutes!
I've put together a small program to reproduce the problem which you can download at: https://www.dropbox.com/s/3m27jjco0e7ye5j/ReproduceBug130.zip?dl=0
You'll need 10+ Twitter users to be able to reproduce the error in a reasonable amount of time (usually under 5 mins).
This is currently a major problem for me, so I'd be very grateful if you could be of assistance.
Thanks,
Josh Keegan
I have a program that polls the Twitter REST API for a number of Twitter Users.
I've been getting the following occasionally:
--- Date : 13/04/2015 14:21:48
URL : https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=JeremyClarkson&include_rts=True&exclude_replies=False&contributor_details=False&count=200&trim_user=False&include_entities=True
Code : 408
Error documentation description : Twitter was not able to perform your query within the Timeout limit of 10000 ms.
The program would run without error for some time (up to a week) and then queries would start timing out. Once one had timed out, more & more will time out until no queries are returning within 10s.
Restarting the program fixes the problem. You can even leave the broken instance still running and start a new instance of the program which will work fine.
I don't believe this to be network related as I have reproduced the error on a Windows Azure instance (which is completely separate from our own hardware that we usually run the application on).
I don't think the queries are even being sent to Twitter because when I leave TCPView open, once the timeouts are happening for all requests, the packet counts & sent and received bytes for each open connection doesn't change.
Up until the end of last week I was running it with about 5 users, but it now has about 40 users. Since I have added the additional users, these errors have started happening far more frequently. Now I'm lucky if it works for 5 minutes!
I've put together a small program to reproduce the problem which you can download at: https://www.dropbox.com/s/3m27jjco0e7ye5j/ReproduceBug130.zip?dl=0
You'll need 10+ Twitter users to be able to reproduce the error in a reasonable amount of time (usually under 5 mins).
This is currently a major problem for me, so I'd be very grateful if you could be of assistance.
Thanks,
Josh Keegan