|
|
Home
Search
Register
Login
Recent Posts
»Forums Index
»Archive (2017 and earlier)
»IQFeed Developer Support
» History LookupError
|
|
| Author | Topic: History LookupError (3 messages, Page 1 of 1) |
 opttrade -Interested User- Posts: 25 Joined: Nov 7, 2016 |
Posted: Nov 13, 2018 08:16 AM
Msg. 1 of 3
Hi,
everyday I'm requesting historical minute data for the last trading day for about 3000 stocks and everyday I get somtimes connection errors for some symbols in the middle of the task. When I re-run the task then there are other symbols affected. The logfile shows an error connecting the history socket
As I've no glue how the client internally is communicating with the Servers but it seem's the IQFeedClient having troubles sending the request. The socket connection from my app to the iqClient is still alive and not broken. The errors (about 10-30 symbols out of 3000) appears never in a row - they are absolutly randomly. I'm using IQFeed Version 6.0.0.5 Any ideas? br Erich |
|
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005 
|
Posted: Nov 13, 2018 11:02 AM
Msg. 2 of 3
Socket error 10060 is a timeout error on the connection from your machine to our servers.
Each request you make to the feed is handled in it's own connection to the server (Create -> Connect -> Request -> Receive -> Close). As a result, if you're spinning through 3000 stocks, that is 3000 different socket connections to the server over the course of however long it takes you to make those requests. We have investigated these sorts of reports a few different times over the years and we've never been able to replicate this reliably or identify a specific cause (all of our tests from both internal and external to our network have not been able to replicate). If it's something that just recently started, you might try resetting your router/modem (most non-enterprise class hardware will occasionally hiccup under heavy connection load). Of course we are happy to help troubleshoot this with you but most of the time, since a simple re-request usually succeeds, most developers choose to simply implement that (as you have) and not worry about it anymore unless the problem gets worse. |
|
opttrade -Interested User- Posts: 25 Joined: Nov 7, 2016 |
Posted: Nov 13, 2018 12:04 PM
Msg. 3 of 3
Hi Steve,
thanks for prompt reply. The problem seems to exist for a longer time, but we started just now to analyze the logs... As we use business connection and enterprise equipment for routing and firewall (Cisco) I personally would exclude problems with it. Maybe the line is to Long between Europe and US  So the simpliest way will be to requery that symbols. Many thanks and br Erich |
|
|