Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott
"I will tell others who want to go into trading that DTN ProphetX is an invaluable tool, I don't think anyone can trade without it..." - Comment from Luther
"I have been using IQFeed now for a few years in MultiCharts and I have zero complaints. Very, very rare to have any data hiccups or anything at all go wrong." - Comment from Public Forum
"Just a quick one to say I'm very impressed so far :) The documentation for developers is excellent and I've quickly managed to get an app written to do historical downloads. The system is very robust and pretty quick considering the extent of data that's available. The support guys have been very helpful too, in combination with the forums it's been plain sailing so far!" - Comment from Adam
"I like you guys better than *******...much more stable and a whole lot fewer issues." - Comment from Philip
"I am keeping IQFeed, much better reliabilty than *******. I may refer a few other people in the office to switch as well." - Comment from Don
"Thank God for your Data Feed as the only Zippers I see are on my pants (LOL), and no more 200 pip spikes to mess up charts." - Comment from Spiro via Email
"I had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum
"If someone needs the best quality data and backfill beyond what their broker provides at a rate that is the best in the industry, I highly recommend IQFeed." - Comment from Josh via Public Forum
"Just a thank you for the very helpful and prompt assistance and services. You provided me with noticeably superior service in my setup compared to a couple of other options I had looked at." - Comment from John
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
Viewing User Profile for: gregsemple
About Contact
Joined: Mar 19, 2005 02:52 PM
Last Post: Mar 25, 2005 12:06 PM
Last Visit: Mar 25, 2005 02:57 PM
Website:  
Location:
Occupation:
Interests:
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
gregsemple has contributed to 3 posts out of 21185 total posts (0.01%) in 6,979 days (0.00 posts per day).

20 Most recent posts:

Alright, for anyone else experiencing difficulty with this problem, here is my workaround.

Basically, use the socket interface for all interaction with IQ Feed (historical data or otherwise), and have a separate "server" process call RegisterClientApp/RemoveClientApp. Having the ActiveX component isolated in the other process fixed about 3-4 stability issues I was having, including a crash on exit. Seems to be something flawed in the connection point disconnect logic, judging from the stack traces. Having a constantly-running server seems to get around these issues.

As a bonus, you get around the nasty bug where a crash in your application causes you to have to manually kill the IQConnect.exe process in order to get further historical data (since the next time you call RegisterClientApp, it won't re-establish the history socket).


I'm following up here since I haven't received a reply.

I didn't see this issue in your buglist at http://www.iqfeed.net/dev/buglist.cfm, does that mean you do not believe this instability is a problem with IQFeed?

Getting frustrated here, thanks for any replies.


Hi,

I'm getting an "Unknown Win32 Exception" while using the sockets interface to historical data. If I comment out the following code, I experience no stability problems:

TcpClient client = new TcpClient("127.0.0.1", 9100);
client.Close();

So, somehow opening the socket causes a crash? I wouldn't believe it but I saw another post about this exact same problem, for instance a post on Oct 2004 by frankzhou, where he provided complete source code to reproduce the problem.

Is this fixed now? I'm using 2.3.0.2, so is this just an issue specific to the beta? If not, is there a proposed workaround? If there is no workaround, can we get this as a "hot fix" - it makes my application pretty unusable since I can't actually get historical data :)

Greg


Time: Fri April 26, 2024 12:34 PM CFBB v1.2.0 5 ms.
© AderSoftware 2002-2003