Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 18:58:10 +0000
Disconnects with Denali
View Count: 1121
| [2020-02-14 19:44:12] |
| nosast - Posts: 290 |
|
I had two disconnects for a few seconds in the last 30 minutes or so. The message log says something about "Data service (sc_exchange2.datafeed) is disabled or unsupported. A software update may be necessary". I'm on 2048 so this release should not be outdated. Happened two times with the same error, while every other feed I use was working fine. How can I solve this? SC Data - All Services | There has been no activity on the network socket for 40 seconds. Will reconnect. | 2020-02-14 13:37:26.437 DTC Client socket (4) | CloseSocket call. | 2020-02-14 13:37:26.438 SC Data - All Services | Disconnected from the server. | 2020-02-14 13:37:26.438 SC Data - All Services | Data feed disconnected. Will reconnect in 2 seconds. | 2020-02-14 13:37:26.438 DTC Client socket (4) | Write in progress. Shutdown being delayed. | 2020-02-14 13:37:26.438 SC Data - All Services | Connecting to the server ds23.sierracharts.com. Port 10048 | 2020-02-14 13:37:28.439 DTC Client socket (2) | Creating socket. | 2020-02-14 13:37:28.440 DTC Client socket (2) | Connecting to IP: 216.1.90.130. | 2020-02-14 13:37:28.440 SC Data - All Services | Connected to server. | 2020-02-14 13:37:28.564 SC Data - All Services | Starting socket receive thread. | 2020-02-14 13:37:28.565 SC Data - All Services | Sending encoding request to server: Binary VLS | 2020-02-14 13:37:28.565 SC Data - All Services | Setting DTC encoding to Binary VLS | 2020-02-14 13:37:28.712 SC Data - All Services | Sending logon request message. | 2020-02-14 13:37:28.712 SC Data - All Services | Received logon response. | 2020-02-14 13:37:28.837 SC Data - All Services | Server Name: SC Real-Time Server. | 2020-02-14 13:37:28.837 SC Data - All Services | Server protocol version: 8. Client protocol version: 8 | 2020-02-14 13:37:28.837 SC Data - All Services | Logon error received from server: Data service (sc_exchange2.datafeed) is disabled or unsupported. A software update may be necessary. | 2020-02-14 13:37:28.837 DTC Client socket (2) | CloseSocket call. | 2020-02-14 13:37:28.837 |
| [2020-02-14 20:02:40] |
| |
|
You can safely ignore that message. It is not related to the disconnect. The disconnect is just simply going to be due to an Internet connectivity issue that you have. It is not on the server side. Over the weekend we are going to set up a real-time data server relay, probably on our London server that you can use. This will require a new release. 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 |
| [2020-02-15 00:36:03] |
| nosast - Posts: 290 |
|
What does it mean to use this London server relay in terms of latency and should I then also use the London trading server instead of Aurora? Also I don't think that the trading connection got interrupted which is located in the same datacenter or at least very close in relation to the route from Frankfurt to Chicago. Another feed I'm using with connection point in Aurora had no disconnects. Can you name a connection IP in the datacenter I can use for testing that actually responds to ping? Just to be clear. This has not been an ongoing issue with the feed and it happened the first time today. If it is of any help attached is a screenshot with the two disconnects. Timezone is Central. Date Time Of Last Edit: 2020-02-16 00:44:23
|
 SNAG_ 2020-02-15 - 01.34.55.png / V - Attached On 2020-02-15 00:35:57 UTC - Size: 7.87 KB - 259 views |
| [2020-02-19 20:40:57] |
| nosast - Posts: 290 |
|
Hey SC, any answer to my questions on latency, order routing server and IPs for testing? Date Time Of Last Edit: 2020-02-19 20:48:49
|
| [2020-02-20 10:13:56] |
| |
|
Using the London server relay will increase latency. Maybe it adds about 50 ms of latency. This is just really only a guess. You will need to make your own observations. We are still in the process of setting up the London relay. We still recommend using the Aurora server for order routing. Can you name a connection IP in the datacenter I can use for testing that actually responds to ping? No not really. The servers will not respond to a ping. But refer to:https://www.sierrachart.com/index.php?page=doc/helpdetails1.php#InternetPortsAndIPAddressesUsedBySierraChartDataServices 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 |
| [2020-02-20 10:58:56] |
| nosast - Posts: 290 |
|
Alright I will test. For the additional latency I think only you could test this as long as the servers don't respond to ping. If it will be around 50ms I can't use it as I often use MIT (which is only implemented for client side) so from my understanding this will add another 50ms before the client gets the trigger to execute the market order. Doesn't make sense to me unless I have lots of disconnects to Aurora Denali. I really think that this could only be a peering or routing problem between the internet carriers you use for broadcasting Denali feed. Otherwise I would also see disconnects to order routing and Rithmic (also Aurora). So connection to London would reduce the hops from Germany to your distribution network and therefore the stability but it will produce more latency. How much is something I would like to know from you once you set this server up. I suppose the connnection from London to your DC in Chicago is on a dedicated line (MPLS?) and not vulnerable to carrier peering and routing. If so the additional latency should be way less then 50ms; maybe more like 5-10 ms for the additional hop. In this case I would make Denali London my standard connection point. |
| [2020-02-21 09:37:36] |
| |
|
We have this set up and we are releasing a new version now and thinking it through we do not really think this is going to add more than 2 ms or so. There is 97 ms between the server in Chicago and the server in London and the retransmission should be below 2 ms or faster. We could also set up a relay in Germany as well. Let us see how the one in London works. New version will be out in about 30 minutes. It is a prerelease. But it is well tested. The option is Global Settings >> Data/Trade Service Settings >> Service Setting >> Use London Relay Server as Primary for Market Data. 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: 2020-02-21 09:38:07
|
| [2020-02-21 09:48:29] |
| nosast - Posts: 290 |
|
Thanks. Will update today and connect to London relay on a second instance to see if there is any notable delay. You said it could be set as primary, so in case connection to LDN is disconnected, will it automatically fail-over to CHI?
|
| [2020-02-21 09:58:09] |
| |
|
Yes.
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 |
| [2020-02-21 10:44:41] |
| nosast - Posts: 290 |
|
Great addition to your distribution network for European traders! Just comparing both feeds in time and sales windows I don't see any notable difference visually or at least it is below 10ms (chart update interval). I will use this relay over the next couple of trading days and see how it works. As you always suggest to connect to Aurora directly it would make sense to have this fail-over also the other way around. Primary Aurora with an option to fall back to LDN relay. Thanks! |
| [2020-06-17 09:31:42] |
| MichaelZ - Posts: 12 |
|
Hello SC Technical Support, It has been a while since this thread was last updated - do you have any new/more recent info about using London Relay Server as primary for market data? I am a relatively new user based in London and wonder whether I should enable this or not. Many thanks! |
| [2020-06-17 11:00:25] |
| |
|
Go ahead and use it if it is helpful to you. That is just something you have to evaluate.
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 |
| [2020-06-17 12:02:52] |
| MichaelZ - Posts: 12 |
|
Thank you, I thought that in relation to #7 you had real latency figures vs. the estimates expressed therein. Thanks! |
To post a message in this thread, you need to log in with your Sierra Chart account: