Home >> Support Board

Support Board

Date/Time: Fri, 26 Apr 2024 00:44:39 +0000

How to Post a Message for Support

How to tune SC to attempt to connect BitMEX at once after disconnect?

View Count: 1624

[2019-03-09 13:42:34] #1 [Go To First Post]
User517260 - Posts: 97
Dear Support, yesterday SierraChart was working with BitMEX good. Reconnect on Failure check-box is always set as you may see on attached screenshot. But after strong impulse connection to BitMEX was lost and didn't try to reconnect at least 5-6 seconds and I had to connect it manually. We use bot on SieraChart and it is very important for us to have SC connection attempt at once after disconnect. How I may tune SierraChart to try reconnect asap? Thanks. Waiting for your reply, Alex.


letter to SC support.jpg / V - Attached On 2019-03-09 13:37:52 UTC - Size: 88.83 KB - 364 views

[2019-03-11 08:22:39] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
If there is a lost connection to the websocket, that would definitively cause a reconnect. Maybe there was a problem with one of the HTTP requests? We would have to see the Message Log at the time. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-03-11 21:31:43] #3 [Go To First Post]
User517260 - Posts: 97
BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Connecting to WebSocket server. \| 2019-03-11 22:28:20 BitMEX Trading Direct socket (1) \| Creating socket. Using TLS 1.2. \| 2019-03-11 22:28:20 BitMEX Trading Direct socket (1) \| Connecting to IP: 54.76.161.42. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Opening WebSocket. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Sending WebSocket handshake. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Header line. HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:20 BitMEX Trading Direct \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:20 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:20 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2019-03-11 22:28:20 Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:20 BitMEX Trading Direct socket (1) \| Shutdown started. Waiting for graceful close. \| 2019-03-11 22:28:20 BitMEX Trading Direct socket (1) \| Socket gracefully closed by remote side. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Disconnected. \| 2019-03-11 22:28:20 BitMEX Trading Direct socket (1) \| Closed. \| 2019-03-11 22:28:20 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:20 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Connecting to WebSocket server. \| 2019-03-11 22:28:23 BitMEX Trading Direct socket (1) \| Creating socket. Using TLS 1.2. \| 2019-03-11 22:28:23 BitMEX Trading Direct socket (1) \| Connecting to IP: 54.76.161.42. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Opening WebSocket. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Sending WebSocket handshake. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Header line. HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:23 BitMEX Trading Direct \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:23 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:23 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2019-03-11 22:28:23 Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Disconnected. \| 2019-03-11 22:28:23 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:23 BitMEX Trading Direct socket (1) \| Shutdown started. Waiting for graceful close. \| 2019-03-11 22:28:23 BitMEX Trading Direct socket (1) \| Socket gracefully closed by remote side. \| 2019-03-11 22:28:23 BitMEX Trading Direct socket (1) \| Closed. \| 2019-03-11 22:28:23 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Connecting to WebSocket server. \| 2019-03-11 22:28:26 BitMEX Trading Direct socket (1) \| Creating socket. Using TLS 1.2. \| 2019-03-11 22:28:26 BitMEX Trading Direct socket (1) \| Connecting to IP: 54.76.161.42. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Opening WebSocket. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Sending WebSocket handshake. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Header line. HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:26 BitMEX Trading Direct \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 403 Forbidden \| 2019-03-11 22:28:26 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:26 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2019-03-11 22:28:26 Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| WebSocket closed. \| 2019-03-11 22:28:26 BitMEX Trading Direct socket (1) \| Shutdown started. Waiting for graceful close. \| 2019-03-11 22:28:26 BitMEX Trading Direct socket (1) \| Socket gracefully closed by remote side. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Disconnected. \| 2019-03-11 22:28:26 BitMEX Trading Direct socket (1) \| Closed. \| 2019-03-11 22:28:26 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2019-03-11 22:28:26 File >> Disconnect selected. \| 2019-03-11 22:28:26 BitMEX Trading Direct \| Disconnected. \| 2019-03-11 22:28:26

[2019-03-12 00:12:24] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We do see a reconnection is occurring here but the connection is being forbidden by BitMex. And actually we understand if there is a 403 error we should stop retrying altogether or at least increase the delay between retries. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-03-12 07:49:16] #5 [Go To First Post]
User517260 - Posts: 97
it was just yesterday situation, I understood why, but initial problem repeated twice - after disconnect SierraChart does not try to connect to BitMEX. No attempts to reconnect. Reconnect setting is ON. I have to connect manually instead of automatic. It is an initial problem and I don't understend why it does not work.

[2019-03-12 08:56:42] #6 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The log above does show this which will prevent future connection attempts: File >> Disconnect selected. \| 2019-03-11 22:28:2 Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-03-12 12:35:19] #7 [Go To First Post]
User517260 - Posts: 97
Thanks for your reply! But as you may see on attached screenshot - Reconnect on Failure is ON, I just had conneced SC, after some time SC lost BitMEX connection and after that didn't try to connect. I posted part of MessageLog after I manually connected and manually disconnected. But initial problem - SC has switched ON "Reconnect on Failure" setting but after SC lost connection with BitMEX no attempts to connect happened. It was second time foar last few days, so it is very important for us to be sure - SC will try to connect BitMEX if connection will be lost. We had success experience of automatic reconnect with Rithmic and CQG datafeed, with AMP Futurees broker, so it warked nice with CME connections, that is why we are surprised with this situation with BitMEX. Could you help us to avoid this problem? Tell us please what we have to do to fix this problem? Thanks, Alex.


to SC support.jpg / V - Attached On 2019-03-12 12:26:05 UTC - Size: 114.26 KB - 308 views

[2019-03-12 17:57:31] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
There should not be a problem and when there is we need to see the Message Log at the time. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-03-12 20:02:35] #9 [Go To First Post]
User517260 - Posts: 97
I have only video https://youtu.be/RhhRLDp7YJw with MessageLog window - I tuned Save Message Log to file after that situation. it is private trade system of my customer so I hided chart. You may see disconnect at 02:00 of video. Hope it is enough to understand a cause of problem with absent reconnect procedure. Thanks! Waiting for your reply, Alex.

[2019-03-12 20:16:49] #10 [Go To First Post]
User517260 - Posts: 97
Oh, pardon, I forgot you are not allowed to send video - please look into attached screenshots - you may see timing from 22:18:08 (SC still connected to BitMEX), 22:18:09 - disconnected, 22:18:10 - disconnected


Reconnect absent problem 22 18 08.jpg / V - Attached On 2019-03-12 20:15:09 UTC - Size: 265.31 KB - 271 views Reconnect absent problem 22 18 09.jpg / V - Attached On 2019-03-12 20:15:17 UTC - Size: 246.75 KB - 415 views Reconnect absent problem 22 18 10.jpg / V - Attached On 2019-03-12 20:15:23 UTC - Size: 246.52 KB - 346 views

[2019-03-12 20:19:08] #11 [Go To First Post]
User517260 - Posts: 97
and at 22:08:51 SC was still disconnected - no attempts to connect during 42+ seconds, so I had to start connect manually. Please help us to avoid this problem because my customer will avoid me )))) Alex.


Reconnect absent problem 22 18 51.jpg / V - Attached On 2019-03-12 20:18:13 UTC - Size: 304.38 KB - 312 views

[2019-03-12 21:19:18] #12 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
None of what you are giving us is acceptable. We require a Message Log in this format at the time you are having a problem. Refer to: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2019-03-12 23:07:16] #13 [Go To First Post]
User517260 - Posts: 97
I restarted SC after that situation and option "Save Message Log to file" was by default off, so I have no chance to send you that MessageLog. So as I understand we have to wait next time this problem happen. Thanks, Alex.

To post a message in this thread, you need to log in with your Sierra Chart account: