At roughly 17:26 EST tonight I had two different instances of IQConnect crash. They are each run on different accounts and the machines are located in different states. Any idea what happened? Likelihood of happening again? Thanks.

I agree with similar situation with IQConnect crashes.
I sent request to support with crash logs several times, but they ignored me.
PS my crashes occurred when connection to server was disconnected and reconnect was in progress.

Hi guys,

Sorry, if I missed a reply on this Skuvv I thought we had emailed, but that must have been someone else. We are aware that users have had issues with reconnections as of late. We are in the process of trying to both stabilize and improve the entire login and reconnect process to allow us to provide a better experience for end users and to make it so when something like this happens, we will be able to troubleshoot the problems better through expanded logging ability.

The new version is currently expected to go to QA later this month and we will get a beta version up just as soon as possible for people to try and see if it resolves all of the issues you have been seeing.

So once again, if you thought I was ignoring you, I apologize, but it is our highest priority item on the books right now and we are certainly doing all we can to remove these kinds of occurrences from our system.

Tim

JonnyB,

I am checking with the server team to see if anything in particular happened around the time you mentioned and will let you know if we find anything.

Tim

Thanks. I have never seen anything happen like that before where IQConnect just crashes. The fact that it occurred simulataneously on different accounts/machines made it even more unusual.

My latest crash log, maybe it help you.

log here

I also had a crash last night, dmp file attached. I'm running 5.1.0.6.

Edit: OK, it looks like it's too large to attach. I can email it if anybody is interested.
Edited by Craig on Jan 12, 2015 at 11:18 AM

Craig, how large is it? Can you try emailing it to Developer support?

Thanks,

It's about 15MB (7z) file.
What is the email address again?

Craig, I just sent you an email from the support address that you can reply to.

I sent it, hopefully it got through.

Sorry for the delay Craig, looks like it didn't go through. I have sent you a PM with alternate options.

After nobody responded, I simply assumed you had the file and deleted it.

Sorry for the delayed reply Craig, we were working with the network team to find a better option for these larger files. Do the crashes you are experiencing still occur around the same time as the re-connection attempts or did we not notice one way or the other on these most recent crashes?

Tim

This particular crash seemed to be during a reconnect. In general, this older version I'm running will be stable for days on end, then suddenly go south, *mostly* during reconnects.

I don't want to tell you guys how to do your job, but some type of mechanism for forwarding crash dumps would save a lot of guessing wouldn't it? At my day j*b we save the PDB information from all our released builds for just this reason. Also, it's easy to get Win32 code to produce mini-dumps on error.

My connection crashed today too-without any attempt to reconnect. This is the first time I experienced iqconnect.exe completely shutting down without any warning. On a positive note, I really like your data/service overall. The reconnection/handling of multiple clients has always seemed an unstable feature of this feed and has caused me to lose data on a number of days over the years I have been using it-I do save full L1 and L2 data so there is no way for me to get them from historical download once the connection is down/not reset properly. I really wish this could be made stable, it would save a lot of trouble to a lot of people who use this feed for serious analytics.

Note that I do mention multiple clients above, but in this case I only had one client/application using the feed.

I wanted to chime in and reiterate what Steve and Tim have mentioned above. It is a top priority for our development team to ensure IQFeed is rock solid. We are testing a new version of IQFeed internally that has had the connection logic re-worked in hopes to make it more reliable under the multitude of ways our customers use our product.

Over the past few years, the number of products that support IQFeed has grown considerably. We work as close as possible with developers to ensure their implementation of our API is robust. Through that work, we listen to feedback and take feedback seriously and are always exploring ways to make our product better.

We anticipate having a beta release available soon that we expect will resolve the issues reported here. As registered developers, we will make this available to you before the general public so you can test and provide feedback. While these issues are impacting only a small fraction of our overall users, I can assure you that not a single person on our team takes these issues lightly.

---

Jay Froscheiser
Vice President, Active Trader Products