Last week my system for downloading tick & EOD data went a little nuts. My code tries to sense if iqconnect has gone brain dead when I attempt to download a small sample of EOD data. If it fails, it attempts to restart iqconnect every 10 minutes. Last week, it got into a restart cycle and never left it. I realized I may have transgressed a little and I've changed my ways. I have rewritten my iqconnect restart application in a different way. So maybe my new approach will be a little less unkind.

However, currently, I'm unable to get any response. I can attach and request, however, nothing gets downloaded. Iqconnect is up, the admin port [9300] is sending heart beat data just fine. But that's all that is happening. All other applications for downloading tick bin or EOD data attach to iqconnect, appears to send their request but nothing returns. The code I had written to download ticker, ticker symbol, news & ticker bin data have all worked fine since the first of the year, until last week

I'm guessing that if someone ends up being a nuisance you cut him off. If that's the case with me please re-enable me or at least let me know what you think is happening. . Let me know whats up.

Thanks

Good morning,

To my knowledge, as long as that heartbeat is being sent from 9300, and it is sending "Connected" as opposed to "Not Connected" there should not be any need to restart IQ. I have seen individual history requests drop, but never in a pervasive manner and certainly not when the level one connection remained.

If that is what you are seeing, I would appreciate if you could try to get me a log. Just enable the lookup logging via the diagnostics app (in the Start menu), and email the resulting log to us so I can try to help understand what is happening.

Everything account related looks fine on my end. And, FYI, it is very seldom we would ever shut off a client, but in the event someone's code runs wild and starts doing weird things, we would most certainly call.

Tim