ahhhhh, I guess that contract expired....

You might change the symbols that end in G6 to end in H6 instead...

-steve

ooops, I noticed in an earlier post that I said I had set logging registry value to
1, but in fact the error shows up only when it is set to 0, probably because of
the speed issue.

I did some remote testing this morning and I am still getting good data and complete requests for all of the symbols requested

I have created a newer version of my application, which shows consistent
errors on my machine. Please try this newer version, which
finds more of the errors.

If anyone else has java installed and can try this on their machines, that would
also be appreciated.

http://www.softwaretruth.com/stevek/dtn/DtnControllerSimple.java

(I also uninstalled my iqfeed 4.1.0.0 beta installation and re-downloaded
and re-installed, but no change was evident.)

I am still not recieving any errors.

I have run through it 4 times from my local machine as well as 4 more times from a remote location. All requests completed and no errors were reported.

well that is disappointing.

it sounds to me like we need to turn on logging
of the iq app, so that we can trace the problem back.

Where do you stand in getting a version of
the iq connection manager which logs faster,
by not closing and reopening the log every time?

A Workaround Seems To Have Been Found!!!!

When I replaced :

mSinSocket.connect(new InetSocketAddress(InetAddress.getLocalHost(), 9100));
which actually connects to my internet address on the local lan: "192.168.1.100"
with :

mSinSocket.connect(new InetSocketAddress("127.0.0.1", 9100));

it all magically started working consistently.

I even have a theory how this could trigger a bug in dtn's code.
In an earlier message I pointed out that most programmers wrongly
think that they will receive a full line of data when they read from a socket.
Even if the sender of the data sends a full line, there is in fact no guarantee
that this will happen. So one possibility is that connecting to
"192.168.1.100" takes a bit longer, routes through a router, etc.. which
can cause a less than full line to occasionally come through; since
the dtn app is probably not expecting this, it gets misparsed and havoc results.

Another, less likely possibility is that my router or msft's ip stack is messing up
loopback connections. But this is inconsistent with the fact that it only happens
with HX (tick data requests).

In any case, I am glad to be thru this horrific experience lasting 6 months, which I wasted
100's of hours on. It would be nice if dtn would compensate me for their
bug with several months of free service.