Hello,

What would be the best way of handling IQConnect disconnects due to local network failure. As of now, I have my application setup so that upon startup, it uses the Lookup socket to load data since the close of the previous day and then appends real-time data from the Level1 socket. When IQConnect disconnects from DTN servers due to a local network failure, and then reconnects, the real-time feed resumes but the data during the "outage" is missing. I want to handle this situation so that the application reloads from the Lookup port upon reconnect and repeats the same process that it runs upon startup.

From the documentation, it looks like utilizing the S,STATS messages on the Admin port is one way to go. I could monitor the Status field in this message and when it changes to "Not Connected", I could flag the condition and wait for a subsequent "Connected" status change and reload the data. Would this be the right way to go?

Thanks.
Edited by USV on May 4, 2015 at 10:50 AM

That would certainly be one way to go. However, if you already have a connection to the Level 1 feed established, you should be getting a S,SERVER DISCONNECTED message when the network outage is detected followed by a S,SERVER CONNECTED message when connectivity is once again restored. Monitoring for those messages would probably be the easiest for you.

Thank you Steve. I guess I didn't look at the docs hard enough :-)

I am wondering why there is this recent surge in disconnect issues. No one seems to know why and it's a relatively new issue.

I am sorry you are having issues, I have replied in your original thread and sent emails in regards to this matter, but given that your issue is unrelated to these posts I will be using email primarily going forward. We can report any new issues found in a separate thread so that it is less confusing to others that might benefit from what we find.

Tim