Roboforex System error code = 336130329

08 Feb 2019, 15:14Roboforex System error code = 336130329#1
terryww2posts: 22since: 22 Nov 2018

Hi,

with one of the brokers (Roboforex) we get this in our logs once per day.

The problem is that upon successful reconnect on the quote stream, we see only heartbeats, no other data. Since we subscribe to market data, we'd expect, upon successful reconnect, to again receive the data we have subscribed to in the first place (before connection interruption and after successful reconnect). We observe this behavior only with this particular broker, with others the behavior is as expected.

Also the error "System error code = 336130329" is only observed with Roboforex and we're not sure why we get it.

Logs:

WARNING: 20190208-08:03:33.933185533: Session <roboforex., CSERVER, FIX.4.4> : the telecommunication link error is detected (Unknown error 336130329 : System error code = 336130329).  
INFO: 20190208-08:03:33.935962771: Session <roboforex., CSERVER, FIX.4.4> : State is changed from Established to Reconnecting.   
INFO: 20190208-08:03:35.258976690: Session <roboforex., CSERVER, FIX.4.4> : the telecommunication link is restored.
INFO: 20190208-08:03:35.259049589: Session <roboforex., CSERVER, FIX.4.4> : State is changed from Reconnecting to AwaitConfirmingLogin.      
INFO: 20190208-08:03:35.476721518: Session <roboforex., CSERVER, FIX.4.4> : InSeqNum is set to 2.   
INFO: 20190208-08:03:35.476802702: Session <roboforex., CSERVER, FIX.4.4> : State is changed from AwaitConfirmingLogin to Established.           
INFO: 20190208-08:03:35.476810110: Session <roboforex., CSERVER, FIX.4.4> : established.  

 

Kind regards

08 Feb 2019, 17:10#2
Panagiotis Charalampousposts: 2168since: 13 Jan 2017

Hi terryww2,

The expected behavior is that when a connection is dropped, you need to resubscribe to the market data. When you say "We observe this behavior only with this particular broker, with others the behavior is as expected.", do you mean that you do not need to resubscribe to market data when connections to other brokers are dropped or that connections are not dropped for other brokers? Also, please let me know which proxy do you use to connect to your Roboforex account.

Best Regards,

Panagiotis

 

 


Head of Community Management at cTrader
08 Feb 2019, 21:27#3
terryww2posts: 22since: 22 Nov 2018

Hi,

 

what we observe with other brokers (using the cTrader platform) is:

1. once subscribed, even if we pull the cable from the server (and force client reconnect), we observe that the stream continues with sequence numbers where left off. Perhaps our conclusion that if a server drops the connection the same would happen as if the client disconnects was not correct?

2. the connection is not closed 1x/day (as e.g. expected from classical exchanges for the "end of day procedure") - we can connect to a broker for a whole trading Week without having to reconnect i.e. having huge sequence numbers e.g. InSeqNum=201281422. Is this expected with cTrader?

 

So this opens a few questions about the integration with cTrader's FIX API:

Is there any trading schedule or are the markets simply open Mon 12:00AM till FR 12:00AM? When are the connections dropped/disconnected (if at all)?

Also we're not sure if this is expected behavior with Roboforex. Perhaps we were too optimistic integrating with cTrader and thinking one integration will work for multiple brokers? What differences between borkers using cTrader can we expect?

 

Kind regards

13 Feb 2019, 09:48#4
terryww2posts: 22since: 22 Nov 2018

With Roboforex we're experiencing also strange connection interrupts. From our logs:

1. "the telecommunication link error is detected: closed by the counterpart"

2. "Cannot logon: after sending the initial Logon message the telecommunication link error is detected (Connection reset by peer : System error code = 104"

 

Since we don't see this kind of disconnects with other brokers using cTrader's FIX connection, we were wondering if you can help us with the investigation.

 

Kind regards

 

13 Feb 2019, 10:39#5
Panagiotis Charalampousposts: 2168since: 13 Jan 2017

Hi terryww2,

Regarding your questions

1. The server does not drop the connection as soon as you pull the cable from the server but when it stops receiving heartbeats for a specific period of time.

2. Yes this is expected

We will investigate the issue with Roboforex.

Best Regards,

Panagiotis


Head of Community Management at cTrader
13 Feb 2019, 15:34#6
Panagiotis Charalampousposts: 2168since: 13 Jan 2017

Hi terryww2,

Can you please tell us the proxy you use and if this happens on demo or live accounts?

Best Regards,

Panagiotis


Head of Community Management at cTrader
13 Feb 2019, 16:15#7
terryww2posts: 22since: 22 Nov 2018

We're using a live account and are connecting to h39.p.ctrader.com.

13 Feb 2019, 16:25#8
terryww2posts: 22since: 22 Nov 2018

After checking the FIX connection info in cTrader's settings again, the address changed to h35.p.ctrader.com. Which one should we use? Should we check daily for updated FIX connection data?

15 Feb 2019, 13:46#9
terryww2posts: 22since: 22 Nov 2018

Any updates or perhaps an answer to the last question?

15 Feb 2019, 14:40#10
Panagiotis Charalampousposts: 2168since: 13 Jan 2017

Hi terryww2,

You can use any of the two host you want but we suggest to use the one displayed in cTrader. cTrader automatically chooses the proxy with the less latency to connect.

Regarding your issue with Roboforex, it seems there was an issue with SSL handshake. We have made some updates to h39.p.ctrader.com. Can you please test it for a while and let us know if the issue has been resolved?

Best Regards,

Panagiotis


Head of Community Management at cTrader