Support Board
Date/Time: Mon, 03 Feb 2025 06:59:49 +0000
Services intermittently connect & disconnect the whole day
View Count: 836
| [2019-10-28 18:18:41] |
| Tooth Fairy - Posts: 79 |
|
SC Futures Order Routing/Data | Connecting to the server futurestrading2.sierracharts.com. Port 11098 | 2019-10-28 13:23:44.098 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2019-10-28 13:23:44.116 DTC Client socket (1) | Connecting to IP: 208.185.224.129. | 2019-10-28 13:23:44.116 SC Futures Order Routing/Data | Connected to server. | 2019-10-28 13:23:44.255 SC Futures Order Routing/Data | Starting socket receive thread. | 2019-10-28 13:23:44.255 SC Futures Order Routing/Data | Sending encoding request to server: Binary VLS | 2019-10-28 13:23:44.255 SC Futures Order Routing/Data | Setting DTC encoding to Binary VLS | 2019-10-28 13:23:44.523 SC Futures Order Routing/Data | Sending logon request message. | 2019-10-28 13:23:44.523 SC Futures Order Routing/Data | Received logon response. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Server Name: SC DTC Server. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Server protocol version: 8. Client protocol version: 8 | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Successfully connected. Connected to SC DTC Protocol server. Service=trading_technologies.trading|SymbolSettings=trading_technologies_v2.trading. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Trading is supported. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Order cancel and replace is supported. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | OCO Orders supported. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Bracket Orders supported. | 2019-10-28 13:23:44.620 SC Futures Order Routing/Data | Connected to data and trading server. | 2019-10-28 13:23:44.620 Triggering next historical data download in queue. | 2019-10-28 13:23:44.620 Triggering next historical data download in queue. | 2019-10-28 13:23:44.620 Triggering next historical data download in queue. | 2019-10-28 13:23:44.620 Triggering next historical data download in queue. | 2019-10-28 13:23:44.620 DTC Client socket (1) | Socket gracefully closed by remote side. | 2019-10-28 13:58:57.840 DTC Client socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-10-28 13:58:57.897 DTC Client socket (1) | Closed. | 2019-10-28 13:58:57.897 Connection to the external service has been lost. | 2019-10-28 13:58:57.897 SC Futures Order Routing/Data | Disconnected. | 2019-10-28 13:58:58.174 Will reconnect to the server in 1.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-10-28 13:58:58.174 SC Futures Order Routing/Data | Connecting to the server futurestrading2.sierracharts.com. Port 11098 | 2019-10-28 13:58:59.268 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2019-10-28 13:58:59.283 DTC Client socket (1) | Connecting to IP: 208.185.224.129. | 2019-10-28 13:58:59.283 SC Futures Order Routing/Data | Connected to server. | 2019-10-28 13:58:59.429 SC Futures Order Routing/Data | Starting socket receive thread. | 2019-10-28 13:58:59.429 SC Futures Order Routing/Data | Sending encoding request to server: Binary VLS | 2019-10-28 13:58:59.429 SC Futures Order Routing/Data | Setting DTC encoding to Binary VLS | 2019-10-28 13:58:59.699 SC Futures Order Routing/Data | Sending logon request message. | 2019-10-28 13:58:59.699 SC Futures Order Routing/Data | Received logon response. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Server Name: SC DTC Server. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Server protocol version: 8. Client protocol version: 8 | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Successfully connected. Connected to SC DTC Protocol server. Service=trading_technologies.trading|SymbolSettings=trading_technologies_v2.trading. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Trading is supported. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Order cancel and replace is supported. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | OCO Orders supported. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Bracket Orders supported. | 2019-10-28 13:58:59.782 SC Futures Order Routing/Data | Connected to data and trading server. | 2019-10-28 13:58:59.782 Triggering next historical data download in queue. | 2019-10-28 13:58:59.783 Triggering next historical data download in queue. | 2019-10-28 13:58:59.783 Triggering next historical data download in queue. | 2019-10-28 13:58:59.783 Triggering next historical data download in queue. | 2019-10-28 13:58:59.783 DTC Client socket (1) | Socket gracefully closed by remote side. | 2019-10-28 14:01:22.208 DTC Client socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-10-28 14:01:22.267 DTC Client socket (1) | Closed. | 2019-10-28 14:01:22.268 Connection to the external service has been lost. | 2019-10-28 14:01:22.268 SC Futures Order Routing/Data | Disconnected. | 2019-10-28 14:01:22.529 Will reconnect to the server in 1.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-10-28 14:01:22.529 -------------------- Denali exchange data feed. Version 2002. Happens only today. |
| [2019-10-28 18:35:09] |
| |
|
What time zone do you have Sierra Chart set to? We need to know so we can check the server log file. If you have an ongoing problem, then we want you to switch to "Server 1". See step 11 here: https://www.sierrachart.com/index.php?page=doc/SierraChartOrderRoutingServiceWithData.php#SetupInstructions Make sure you do this though when you no longer have any working server-side bracket orders. 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 Date Time Of Last Edit: 2019-10-28 18:37:11
|
| [2019-10-28 18:42:57] |
| nosast - Posts: 312 |
|
Same here... Frequent disconnects to order routing. Never happened before and today it happened 5 times in around 2 hours. Internet without any issues. Also ping to a Sierra IP without any latency issues or interupts. DTC Client socket (3) | Socket gracefully closed by remote side. | 2019-10-28 13:36:21.102 Connection to the external service has been lost. | 2019-10-28 13:36:21.106 DTC Client socket (3) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-10-28 13:36:21.106 DTC Client socket (3) | Closed. | 2019-10-28 13:36:21.106 SC Futures Order Routing/Data | Disconnected. | 2019-10-28 13:36:21.382 Will reconnect to the server in 1.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-10-28 13:36:21.382 SC Futures Order Routing/Data | Connecting to the server futurestrading2.sierracharts.com. Port 11098 | 2019-10-28 13:36:22.627 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2019-10-28 13:36:22.648 DTC Client socket (1) | Connecting to IP: 208.185.224.129. | 2019-10-28 13:36:22.649 SC Futures Order Routing/Data | Connected to server. | 2019-10-28 13:36:22.918 Date Time Of Last Edit: 2019-10-28 18:46:41
|
| [2019-10-28 18:52:06] |
| |
|
What time zone do you have Sierra Chart set to? We are looking into the issue. We do observe some problem. 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 Date Time Of Last Edit: 2019-10-28 18:58:21
|
| [2019-10-28 19:05:17] |
| Tooth Fairy - Posts: 79 |
|
Time zone setting is New York.
|
| [2019-10-28 19:07:17] |
| |
|
We rolled back to a prior revision of the order routing server. We are not sure what the problem is but we did notice a high CPU usage condition apparently on one of the threads. Let us see if this is resolved and then we need to figure out what the problem is. You would have noticed one more disconnect a couple of minutes ago when we did that. 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 Date Time Of Last Edit: 2019-10-28 19:07:23
|
| [2019-10-28 19:17:24] |
| nosast - Posts: 312 |
|
My timezone setting is central so the exchange timezone.
|
| [2019-10-28 19:21:31] |
| |
|
Let us know if you notice a further issue. There was a problem earlier due to a software update but it is not clear what the issue was. It will take some time to determine what the issue is. We want to know that it is resolved. And that answer is going to help us.
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 Date Time Of Last Edit: 2019-10-28 19:21:51
|
| [2019-10-28 19:23:24] |
| nosast - Posts: 312 |
|
will report after close
|
| [2019-10-28 20:06:10] |
| |
|
We found the problem. We are fixing it now. We do apologize for the issue. Obviously this looks bad when we have a lot of users on CQG with connectivity problems and we are recommending this service to solve them and then we have this problem but there was a very specific reason for the issue. It was not a lower level network connectivity issue. There was an internal signaling issue, triggering the disconnect of multiple users at once. 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 Date Time Of Last Edit: 2019-10-28 20:09:51
|
| [2019-10-28 20:13:54] |
| nosast - Posts: 312 |
|
I had no further disconnects after you rolled back to the previous revision. Thanks for your immediate analysis and honestly naming the root cause. |
To post a message in this thread, you need to log in with your Sierra Chart account: