Login Page - Create Account

Support Board


Date/Time: Thu, 28 Mar 2024 19:56:20 +0000



Reconnects

View Count: 1158

[2014-05-26 07:09:38]
GPST10 - Posts: 139
Why SC reconnects sometimes when markets are active. It happens not very often but consistently. Anybody else noticing the behavior?
[2014-05-26 07:14:38]
Sierra Chart Engineering - Posts: 104368
What Data or Trading service are you using that you noticed this with? This is critical to know.

Sierra Chart supports connections to numerous services. Every service is unique in of itself and has its own set of issues.

Therefore, your question about anyone else noticing the behavior, has no relevancy.
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
[2014-05-26 13:55:07]
GPST10 - Posts: 139
I'm using two instances of SC with TA and SC Exchange data.

[2014-05-26 19:46:31]
Sierra Chart Engineering - Posts: 104368
Which instance is having the problem?

We need to see the Message Log at the time of the problem. Here are the instructions:
https://www.sierrachart.com/index.php?l=PostingInformation.php#log
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
[2014-05-27 06:58:13]
GPST10 - Posts: 139
I just sent my log from the copy just reconnected

[2014-05-27 07:14:14]
Sierra Chart Engineering - Posts: 104368
At first we were not sure what you are referring to in this particular case because we could not see a connection lost, but we think you are referring to this:

Real-time data for symbol FDAXM4 is currently unavailable. | 2014-05-27 02:54:45
Real-time data for symbol FESXM4 is currently unavailable. | 2014-05-27 02:54:45
Real-time data for symbol FGBLM4 is currently unavailable. | 2014-05-27 02:54:45
Real-time data for symbol FDAXM4 has been restored. | 2014-05-27 02:54:50
HD Request # 53 - Downloading Intraday chart data for FDAXM4 to the file FDAXM4.scid. Service: eurex | 2014-05-27 02:54:50
HD Request # 53 - Download start Date-Time: 2014-05-27 02:54:43.0 | 2014-05-27 02:54:50
HD Request # 53 - Using server: scdf1.sierracharts.com port 10149 | 2014-05-27 02:54:50
Resolved address ds6.sierracharts.com to IP 8.18.161.131 | 2014-05-27 02:54:50
The network socket is connected. | 2014-05-27 02:54:50
HD Request # 53 - Sending historical data logon request message. | 2014-05-27 02:54:50
Real-time data for symbol FESXM4 has been restored. | 2014-05-27 02:54:50
Real-time data for symbol FGBLM4 has been restored. | 2014-05-27 02:54:50

This occurs rarely and it has to do with either maintenance being done on the server which may interrupt the connection for two seconds or there is some other connectivity issue on the backend causing this. In all cases, there is no data loss because the historical data is automatically restored.

We do not see this as a problem. It is infrequent, there is no data loss, and the streaming feed in this case was only interrupted for five seconds.
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: 2014-05-27 07:14:55
[2014-05-28 07:23:18]
GPST10 - Posts: 139
I sent one more log, may be it is normal because it does take only few seconds but could you check again please at 3:13:58
[2014-05-28 07:27:52]
GPST10 - Posts: 139
One more LOG I sent for second instance just in case you need - it reconnected as well.
[2014-05-28 07:30:01]
Sierra Chart Engineering - Posts: 104368
Yes we know about that. We had to do a software update. The interruption was only two seconds. All of the data was restored.

This is considered acceptable.

Now what is unacceptable is the outage we had yesterday that went on for more than an hour. The underlying problems were external having to do with the Barchart authorization system and a malfunction of the operating system but we are addressing both of those issues.

Sometimes there may be servers that are taken off-line or software updates. This causes an interruption for two seconds while the connectivity is transferred to another server. This is acceptable. If it is not acceptable, then we recommend not using the data feed. Although these incidents are infrequent.

We are not quite sure why are you are pointing these out to us again after we previously explained this. While we do our best, our focus is on high reliability and avoiding incidents like yesterday. Small maintenance issues which cause a transferring to another server and interruption of two seconds without data loss because the data is automatically filled in, should not be an issue. If this is a problem once again we recommend you use another data feed.

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: 2014-05-28 07:41:11
[2014-05-28 07:40:05]
Sierra Chart Engineering - Posts: 104368
And any incidents you have seen in prior days, probably are unrelated to this. You may have had a disconnect from TransAct.
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
[2014-05-28 08:19:35]
GPST10 - Posts: 139
I agree it was really short time only just making sure. Yes the prior disconnects the same - I wasn't sure initially how long it took.
Thanks
[2014-05-28 08:33:59]
Sierra Chart Engineering - Posts: 104368
If we have to do some kind of an emergency software patch, we make sure the interruption is under one second. We have a very fast updating method. On your side you may notice it for more like 3 to 4 seconds. But that should be about it.
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

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

Login

Login Page - Create Account