aerich48
30 May 2019, 15:29

FIX available host jumps from h55.* to h33.* and back without warning

Thanks for that check !

You may be right.

To recap, the application always does this when required:

1. Logon to Quotes

2. Get market data

3. Log out of Quotes

4. Close the Quotes socket

It does this periodically, so that there is reasonable continuity of prices. It *usually* works well, and very fast.

But the application might be closing the Quotes socket too soon after sending the logout message, thus the logout *might* not be getting through, and the session might remain logged in, as you suggest. I will change the implementation to use a delay after sending the Logout(5) message, and see what happens.

Thanks again.

aerich48
30 May 2019, 14:06

FIX available host jumps from h55.* to h33.* and back without warning

Thanks for your info and suggestion.

About 1 hour after my last post, I got this report from the FIX trading application, which might help:

Logging Into Quotes...
8=FIX.4.4|35=A|49=pepperstone.3292158|56=CSERVER|50=QUOTE|57=QUOTE|34=1|52=20190530-10:58:25.000|98=0|108=0|141=Y|553=3292158|554=twcfk3Lj|
'Fx.logonsesn()': 'Fix.decmsg': Empty Response Stream

The problem persisted on re-try a number of times.

The host this time was:

h55.p.ctrader.com

The date stamp is UTC, so this may shed light on the problem.

Thanks.

P.S. The problem was then solved by going back again to host "h33.p.ctrader.com", as before (!)