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)




"Everything is working great ! Very impressive client. The news refreshes better and is more pertinent than the ******* feed I paid $ 100/month for. I Also like the charts a lot." - Comment from Leon
"If you want customer service that answers the phone, your best bet is IQFeed. I cannot stop praising them or their technical support. They are always there for you, and they are quick. I have used ****** too but the best value is IQFeed." - Comment from Public Forum
"Boy, probably spent a thousand hours trying to get ******* API to work right. And now two hours to have something running with IQFeed. Hmmm, guess I was pretty stupid to fight rather than switch all this time. And have gotten more customer service from you guys already than total from them… in five years." - Comment from Jim
"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan
"My broker in Davenport suggested I give you a try as he uses your service and says its the best." - Comment from Bill via RT Chat
"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"If you are serious about your trading I would not rely on IB data for serious daytrading. Took me a while to justify the cost of IQ Feed and in the end, it's just a 2 point stop on ES. Better safe than sorry" - Comment from Public Forum
"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe
"After all the anxiety I had with my previous data provider it is a relief not to have to worry about data speed and integrity." - Comment from Eamonn
"I've been using Neoticker RT with IQFeed for two months, and I'm very happy with both of the products (I've had IQFeed for two years with very few complaints). The service from both companies is exceptional." - Comment from Public Forum
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 21196 total posts (0.01%) in 7,001 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: Sat May 18, 2024 11:45 PM CFBB v1.2.0 4 ms.
© AderSoftware 2002-2003