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)




"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"Thank you so much - awesome feed, awesome service!" - Comment from Greg via Email
"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
"I was with ******* for 4 years at $230 a month, this is a huge savings for me, GOD BLESS YOU PEOPLE," - Comment from T.S. via Email
"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"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
"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 was on the phone with a friend who uses CQG and right after the Fed announcement, CQG was as much as 30 seconds behind DTN.IQ. Some quotes were off by as much as 15-18 cents. Your feed never missed a beat." - Comment from Roger
"Everything is working amazing now. I'm already impressed with the true-tick feed of IQFeed and it's ability to support my 480 symbol layout." - Comment from Tyler via Email
"It’s so nice to be working with real professionals!" - Comment from Len
Home  Search  Register  Login  Blogs Recent Posts

Information on Various DTN Products:
DTN IQFeed | DTN ProphetX | DTN Ag | NxCore
Follow DTN_IQFeed on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Product Support »DTN.IQ Client Software Support »Beta 5.2.0.6 not connecting after issuing the CONNECT command
Author Topic: Beta 5.2.0.6 not connecting after issuing the CONNECT command (10 messages, Page 1 of 1)

jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015


Posted: Jan 28, 2016 04:20 PM          Msg. 1 of 10
I've run some tests with the beta 5.2.0.6 and it does not connect after issuing:

S,CONNECT

It simply does nothing, if I click the connect button it connects OK.

Under the 5.1.3.1 version it works as expected, I issue AUTOCONNECT OFF and then CONNECT and it works, no problem.

The beta 5.2.0.6 seems to reconnect when I issue CONNECT after a network loss.
It is only the first time after launching the client that CONNECT does not work???

I'm requesting the 5.1 protocol by the way. Here is the the input from the client:

S,CURRENT PROTOCOL,5.1,\r\n
S,REGISTER CLIENT APP COMPLETED,\n
S,CURRENT LOGINID,xxxxxxx,\n
S,CURRENT PASSWORD,xxxxxxx,\n
S,LOGIN INFO SAVED,\n
S,AUTOCONNECT OFF,\n
S,STATS,,,0,0,1,1,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.15,0.0,,\n
S,STATS,,,0,0,1,2,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.22,0.22,,\n
S,STATS,,,500,0,1,0,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.28,0.14,,\n
[...]

Issuing multiple CONNECT and never connects.

Using wine under Linux:

wine-1.9.0-36-g43197e6

Edited by jrodrigo on Jan 28, 2016 at 04:40 PM

DTN_Tim Walter
-DTN Guru-
Posts: 1093
Joined: Apr 25, 2006


Posted: Jan 29, 2016 08:45 AM          Msg. 2 of 10
Thanks for the report. We will take a look at it.

Tim

jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015


Posted: Jan 31, 2016 01:33 PM          Msg. 3 of 10
Thanks Tim...

I continue to run the beta version and I can confirm that the the connection dialog pops up some times
and we are back to the 'procedural CONNECT impossibility' bug, human action is required (ie: click on the connect button).

I've run some more tests with the Diagnostics tool.
First of all, running the full test suite the application crashes.
I've read on the forum that this is due to the COM interfacing that is going to be removed.

There is some strange behaviour when launching the Diagnostic's traceroute.
I have activated the raw sockets capability for wine, so the Diagnostic's ping test works ok.
But the traceroute test reports Error:11010 (+very long timeout) for all the intermediate hops,
only the last hop returns the timing info.

Tracerouting the same boxes with the native Linux traceroute tool yields a lot more information,
the native tool manages to get timing info for some of the first hops (and some times the last one).

If this tracerouting capability is used by the iqconnect.exe application itself this behaviour could be bad.

In addition I would like to know if you are planning any more beta releases (maybe fixing the CONNECT issue),
because this beta seems to work better under wine.

The random crashes on iqconnect.exe start and shutdown under wine seem to have disappeared.
I knew that those crashes were related to the wine - iqconnect.exe interaction and it is nice that they are gone.

I would like to continue using the beta on a daily basis but the CONNECT problem impedes me to do so.
I have to install different iqconnect versions back and forth.

Thanks again Tim.

DTN_Tim Walter
-DTN Guru-
Posts: 1093
Joined: Apr 25, 2006


Posted: Feb 1, 2016 07:23 AM          Msg. 4 of 10
Hello,

Tracerouting is never used within the application. That is more of a tool for when our service team needs to analyze the connectivity to our servers, so if you are only seeing it there I would not worry about it much, but I'll take a look nonetheless.

We will have a new betas and we are looking at the CONNECT command on initial connect not working currently and will reply when we get it resolved.

Tim

jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015


Posted: Feb 1, 2016 08:52 AM          Msg. 5 of 10
Thanks Tim...

Well after starting and stopping iqconnect.exe beta for a good number of times during a 12 hour period I have some not so random crashes.

It seems to always follow a similar path through _XlcDestroyLocaleDataBase (some times RtlRaiseException is on the stack too):

Backtrace:
=>0 0xffffe430 __kernel_vsyscall+0x10() in [vdso].so (0x0152b7f8)
1 0xf73e7f47 gsignal+0x46() in libc.so.6 (0x0152b7f8)
2 0xf73e9616 abort+0x155() in libc.so.6 (0x0152b7f8)
3 0xf7425e72 in libc.so.6 (+0x6be71) (0x0152b7f8)
4 0xf742ba5a in libc.so.6 (+0x71a59) (0x7d9df1e8)
5 0xf742c6a8 in libc.so.6 (+0x726a7) (0x7d9df1e8)
6 0x7de700d4 _XlcDestroyLocaleDataBase+0x83() in libx11.so.6 (0x7d9be9c0)
7 0x7de74cb0 in libx11.so.6 (+0x4ecaf) (0x7dd10008)
8 0x7de7c4b6 _XCloseLC+0x75() in libx11.so.6 (0x7dd10008)
9 0x7de7c500 _XlcCurrentLC+0x2f() in libx11.so.6 (0x7dd10008)
10 0x7de752ed _Xlcmbstowcs+0xdc() in libx11.so.6 (0x7dd10008)
11 0x7de753d3 _Xmbstowcs+0x32() in libx11.so.6 (0x7dd10008)
12 0x7de8a86e in libx11.so.6 (+0x6486d) (0x7dd10008)
13 0x7de889c6 _XimLocalOpenIM+0x3f5() in libx11.so.6 (0x7da06360)
14 0x7de86e57 _XimOpenIM+0xf6() in libx11.so.6 (0x7da06360)
15 0x7de6c837 XOpenIM+0x46() in libx11.so.6 (0x0152dff8)
16 0x7dff0247 in winex11 (+0x50246) (0x0152dff8)
17 0x7dff1461 in winex11 (+0x51460) (0x0152e028)
18 0x7dfed783 in winex11 (+0x4d782) (0x0152e0e8)
19 0x7dfe61e1 X11DRV_WindowPosChanging+0x320() in winex11 (0x0152e178)
20 0x7eb6105f in user32 (+0xa105e) (0x0152e2c8)
21 0x7eb5cab9 in user32 (+0x9cab8) (0x0152e488)
22 0x7eb5642f CreateWindowExA+0x18e() in user32 (0x0152e718)
23 0x1023255c in mfc110 (+0x23255b) (0x0152e784)
24 0x1022d058 in mfc110 (+0x22d057) (0x0152e7f0)
25 0x1021b05a in mfc110 (+0x21b059) (0x0152e848)
26 0x1021b2f8 in mfc110 (+0x21b2f7) (0x0152e860)
27 0x1021a9dc in mfc110 (+0x21a9db) (0x0152e87c)
28 0x0040a8fd in iqconnect (+0xa8fc) (0x004acc34)
29 0x00613c98 (0x00613cc0)
0xffffe430 __kernel_vsyscall+0x10 in [vdso].so: popl %ebp


Could be a wine issue or maybe something going unhandled it is hard to tell. I leave you a log file with multiple occurences.

By the way I'm starting wine in X11 synchronous mode:

WINEDEBUG=-all,+synchronous


wine-1.9.0-36-g43197e6



File Attached: dtn.iqconnect.log.zip (downloaded 225 times)

DTN_Tim Walter
-DTN Guru-
Posts: 1093
Joined: Apr 25, 2006


Posted: Feb 1, 2016 09:10 AM          Msg. 6 of 10
Are you getting a dmp or mdmp file created in your Docs\DTN\IQFeed directory by chance?

Tim

jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015


Posted: Feb 1, 2016 10:44 AM          Msg. 7 of 10
The only files that I have under Docs are:

Docs/
Docs/res
Docs/res/style.css
Docs/res/image003.jpg
Docs/DDE.html
Docs/DDE.htm


Keep in mind that this crash is happening launching and closing iqconnect.exe, it is not a crash on operation. Could be cleanup or initializing issues.

Should I activate something on the iqconnect?
BTW I have totally restricted the wine debugger, so no crash notifier popup comes up nor the debugger kicks in, it justs crashes;
in this way I can get to restart iqconnect daemon style if a crash happens during operation.

DTN_Tim Walter
-DTN Guru-
Posts: 1093
Joined: Apr 25, 2006


Posted: Feb 1, 2016 10:46 AM          Msg. 8 of 10
Ok, I have seen where WINE does not create the crash file before, I was hoping though.

Thanks for checking.

Tim

jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015


Posted: Feb 1, 2016 02:02 PM          Msg. 9 of 10
I'm starting to think that this comes from a long running wineserver...
I cannot force the dumps under a fresh wineserver.

I will restart a fresh wineserver with iqconnect each time and monitor this dumps for some hours/days,
we'll see if it is a wineserver issue.
 

 

Time: Tue December 12, 2017 7:17 PM CFBB v1.2.0 16 ms.
© AderSoftware 2002-2003