QuantDeveloper/ TT connectivity and other issues

<IMG SRC="http://ken-okabe.net/TTFIXlog.PNG">
</IMG>

<IMG SRC="http://ken-okabe.net/FIXadapterConsole.PNG">
</IMG>

The above is the log I get from QD and demoFIXadapterCondole.
I'm sure password through alright because I trid to input false password on purpose, then I saw FIXadapter rejected the connection for password mismatch.
Looks like it connect once, and kicked out for some reason, and reconnect on another try.

Thanks for advice.
Regards,

Smooth.
 
If you do reconnect, then it's fine. FIX is very careful with message sequence numbers, so that if you go out of synch for some reason, you should manually examine message logs and then take some action - pain in the back in general, though pretty robust. That's why we reset sequence number on login/logout. Otherwise you need to go to config file and change reconnect settings (this could be a good practice when you are 100% in production mode).

Are you able to request instruments from TT FIX in QD?

Regards,
Anton
 
Hi Smooth,

QuantDeveloper uses the QuickFix engine for its FIX messaging, maybe you can look at the quickfix logs and it will give you a clue what is going wrong?

I develop with the quickfix engine myself and i know that it can be very picky about message formats and so on.

look for a file something like fix/logs/*.events

I have had the experience that the quickfixengine when it finds a message it doesn't like it will spit out a message in that log file and then reject the session.

In your case i don't see any reject messages in your TTFix log so i don't think thats necessarily exactly your problem, but i've found useful clues in those logs in the past so they are good to know about.

If you'd be willing to post a zip file w/ a demo app that produces your problem i'd be happy to try it against my Fix adapter. (i have a copy of QD installed i can try it with)
 
Quote from QuantDeveloper:

If you do reconnect, then it's fine. FIX is very careful with message sequence numbers, so that if you go out of synch for some reason, you should manually examine message logs and then take some action - pain in the back in general, though pretty robust. That's why we reset sequence number on login/logout. Otherwise you need to go to config file and change reconnect settings (this could be a good practice when you are 100% in production mode).

Are you able to request instruments from TT FIX in QD?

Regards,
Anton
More...

Anton,

Thanks for your support.

No, not able to request TT instruments because it says no connection established etc.
So, basically, I understand that the configuration is correct, but for unknown reason, the message sync is not properly done, and QD forces the connection reset.
Well, I hope this sort of problem only occurs on SIM-A environment. As long as it works on production mode, it should be ok, but the problem is I am stuck here and cannot procceed further.

Regards,
Smooth
 
Quote from market_hacker:

Hi Smooth,

If you'd be willing to post a zip file w/ a demo app that produces your problem i'd be happy to try it against my Fix adapter. (i have a copy of QD installed i can try it with)
More...

The demo application (the one included in QD install) uses the same FIX config and log dirs as QuantDeveloper, so that once you can connect to TT FIX Adapter from QD, you can do it from any demo application...

Regards,
Anton
 
Quote from SmoothTraderFX:

Anton,

Thanks for your support.

No, not able to request TT instruments because it says no connection established etc.
So, basically, I understand that the configuration is correct, but for unknown reason, the message sync is not properly done, and QD forces the connection reset.
Well, I hope this sort of problem only occurs on SIM-A environment. As long as it works on production mode, it should be ok, but the problem is I am stuck here and cannot procceed further.

Regards,
Smooth
More...

Have you tried to clean your message logs manually?

Regards,
Anton
 
Quote from SmoothTraderFX:

Yes, I even reinstalled QD.
More...

You better check it manually because uninstall doesn't delete files that you created (logs, components, data, etc.) Like "saved game" files, you know :)

Regards,
Anton
 
You must log in or register to reply here.
Back
Top