Support Board
Date/Time: Mon, 09 Jun 2025 18:55:22 +0000
DOM freezing at market open again
View Count: 823
| [2022-11-29 15:11:44] |
| User449884 - Posts: 170 |
|
Are you guys doing work on the system? Market is freezing at the open for 20-30 secs on the DOMS thanks |
| [2022-11-29 15:40:36] |
| Sierra_Chart Engineering - Posts: 19872 |
|
No not at all. There were no problems on the Denali Data Feed server side like this. Was the user interface of Sierra Chart in a frozen/inoperable state when this occurred? 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-11-29 16:08:08] |
| User449884 - Posts: 170 |
|
I didnt try to click anything. But all futures markets were frozen
|
| [2022-11-29 17:06:21] |
| Rui S - Posts: 200 |
|
Are you guys doing work on the system? Market is freezing at the open for 20-30 secs on the DOMS
thanks Yes, I had the exact same problem at that precise time and needed to disconnect and reconnect. |
| [2022-11-29 17:11:29] |
| StarLight - Posts: 28 |
|
Lots of reconnection. DTC Client socket (1) | Timed out waiting for shutdown. Performing an immediate socket close. | 2022-11-29 12:01:27.317 DTC Client socket (1) | Closed. | 2022-11-29 12:01:27.317 DTC Client socket (3) | Timed out waiting for shutdown. Performing an immediate socket close. | 2022-11-29 12:01:27.317 DTC Client socket (3) | Closed. | 2022-11-29 12:01:27.317 DTC Client socket (4) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2022-11-29 12:01:54.579 * DTC Client socket (1) | Deleting network socket now after delay. | 2022-11-29 12:01:57.317 DTC Client socket (3) | Deleting network socket now after delay. | 2022-11-29 12:01:57.317 DTC Client socket (4) | Timed out waiting for shutdown. Performing an immediate socket close. | 2022-11-29 12:01:57.317 DTC Client socket (4) | Closed. | 2022-11-29 12:01:57.317 DTC Client socket (2) | Timed out waiting for shutdown. Performing an immediate socket close. | 2022-11-29 12:02:27.318 DTC Client socket (2) | Closed. | 2022-11-29 12:02:27.318 DTC Client socket (4) | Deleting network socket now after delay. | 2022-11-29 12:02:27.318 DTC Client socket (2) | Deleting network socket now after delay. | 2022-11-29 12:02:57.318 Orders was freezing too. |
| [2022-11-29 18:11:42] |
| Sierra_Chart Engineering - Posts: 19872 |
|
Regarding post #5, this is an Internet connectivity issue on your side. And also we do not even know what server is even involved from that log since it is incomplete. It does not help to provide us an incomplete log. However, this indicates a connectivity issue on your side: DTC Client socket (4) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2022-11-29 12:01:54.579 * ---- Regarding the other posts, once again there was no indication of any problem on our side and we were specifically monitoring all of the connections at the time and everything was normal and fine. Peak bandwidth usage at the open was nowhere near capacity. Not even 1/3. We did not observe the data feed stopping. It may have stopped in your case, but due to connectivity issues elsewhere. We would like to know though what server you were connected to if you have the Message Log still available at the time this occurred. Instructions to provide this: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2022-11-29 18:57:46] |
| StarLight - Posts: 28 |
|
Thank Support for your response. After I posted to the forum, the connection issued was gone. My youtube and twitter connection was doing well while the connection issues perceived earlier. As per your suggestion, I moved away from my usual trade desk for today, might be wifi issue. As your request: HD Request # 19 | Using server: ds23.sierracharts.com port 10150 | 2022-11-29 12:00:24.121 MESZ22_FUT_CME [C] 1 Min #3 | Performing a full recalculation because it has been tagged. Chartbook: 2022_LIVE.cht | 2022-11-29 12:00:24.140 Thank you. |
| [2022-11-29 20:15:34] |
| Rui S - Posts: 200 |
|
We would like to know though what server you were connected to if you have the Message Log still available at the time this occurred.
The data feed really froze at the opening on this connection. My PC was also connected to another 2 SC servers (or at least 2 different connections) and those did not stop. Just the instance with the DOM did. Please believe me - I can assure you this is not on my side (I wish it was), as I have another data feed, 2 high speed internet connections, etc., etc. Here you have the requested info: Teton CME Order Routing | Firm: Dorman | 2022-11-29 14:29:06.820 Teton CME Order Routing | Connecting to the server futurestrading10.sierracharts.com. Port 11091 | 2022-11-29 14:29:06.820 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2022-11-29 14:29:06.868 DTC Client socket (1) | New receive buffer size: 5242880 | 2022-11-29 14:29:06.868 DTC Client socket (1) | Connecting to IP: 208.185.224.129. | 2022-11-29 14:29:06.868 Teton CME Order Routing | Network connection to server complete. | 2022-11-29 14:29:07.009 Teton CME Order Routing | Starting socket receive thread. | 2022-11-29 14:29:07.009 Teton CME Order Routing | Sending encoding request to server: Binary VLS. Compression: none | 2022-11-29 14:29:07.009 Teton CME Order Routing | Setting DTC encoding to Binary VLS | 2022-11-29 14:29:07.423 Teton CME Order Routing | Sending logon request message. | 2022-11-29 14:29:07.423 Teton CME Order Routing | Received logon response. | 2022-11-29 14:29:07.564 Teton CME Order Routing | Server Name: SC DTC Server. Build=43909M. | 2022-11-29 14:29:07.564 Teton CME Order Routing | Server protocol version: 8. Client protocol version: 8 | 2022-11-29 14:29:07.564 Teton CME Order Routing | Successfully connected. Connected to SC DTC Protocol server. Service=cme_ilink.trading|SymbolSettings=cme_ilink_live.trading. | 2022-11-29 14:29:07.564 Date Time Of Last Edit: 2022-11-29 21:02:29
|
| [2022-12-01 00:01:48] |
| Sierra_Chart Engineering - Posts: 19872 |
|
That is for the order routing. Not market data. So we still do not know what the server was that you were connected to for market data. The problem is not occurring at the server level. It must be ISP (Internet connectivity) related. We are not necessarily saying it is your ISP. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-12-01 00:02:48
|
| [2022-12-01 02:14:54] |
| ertrader - Posts: 684 |
|
I experienced a multi-second delay right after the open today 11/30/22 at approximately 9:31 EDT.(I'm in Houston area with Comcast and did not have any other internet connectivity issues at the time). Fortunately I was not in a trade. I did not disconnect and reconnect ...real-time data started again on its own. This happened a few days ago too. Where do you look to see the server if it's not the message shown above? I could not find the server listing you describe in my message log nor in any of the various server settings. (There is one for Rithmic order routing but that is not what you are asking for because I use SC real-time data) I have turned heartbeat monitoring on and will monitor during the open tomorrow. It is odd because during much more extreme market action later today, real-time data was keeping up just fine. Date Time Of Last Edit: 2022-12-01 02:58:13
|
| [2022-12-01 02:51:54] |
| ertrader - Posts: 684 |
|
Also, since updating to the latest SC version 2457, when first starting SC and after my charts load, I have to disconnect/reconnect 2-3 times to get real-time data to start. The upper left data connection box is green as always...but no real-time data without disconnect/reconnect 2-3 times.
Date Time Of Last Edit: 2022-12-01 02:57:03
|
| [2022-12-01 11:20:03] |
| User820791 - Posts: 15 |
|
I also need to intervene and say that I've tried every single thing in my power to make DOM run smooth and I just cannot do it. It feels it cannot run lower than around 60-70ms chart update interval; also, it skips data on fast moves like on the open. Spent entire days messing with stuff and I just don't know what to do anymore at this point. I love sierra but I just cannot trade like this in live conditions. Like I mentioned in previous posts, on replay it functions completely perfect, behaves at the same level as every other DOM competitor. I've compared side by side with Jigsaw and Bookmap Pro on LIVE conditions and they are WAY smoother and update much faster without any stuttering. Having said that, I know that sierra is capable of performing extremely smooth and fast because I asked some buddies to record the open and I've seen it updating extremely fast on live conditions. Could this be an issue related to the geographical location of certain clients? And the distance to sierra servers? Because I know 3 people from my country (Portugal) and they all experience lack of smoothness. Waiting patiently for an answer. Thank you. Date Time Of Last Edit: 2022-12-01 11:22:13
|
| [2022-12-01 11:29:03] |
| Sierra_Chart Engineering - Posts: 19872 |
|
Regarding post 12, refer to: Chart Trading and the Chart DOM: Improving Performance Of Chart / Trade DOM Could this be an issue related to the geographical location of certain clients?
Any time, you are outside of the internal network, and you are using the public Internet for data, yes there absolutely can be problems which are outside of our control. Including the data feed pausing due to packet loss outside of our infrastructure! Refer to:Prices / Data Falling Behind: 4.12 - Sierra Chart Exchange Data Feeds 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-12-01 11:31:01
|
| [2022-12-01 11:46:34] |
| Rui S - Posts: 200 |
|
I experienced a multi-second delay right after the open today 11/30/22 at approximately 9:31 EDT.(I'm in Houston area with Comcast and did not have any other internet connectivity issues at the time). Fortunately I was not in a trade. I did not disconnect and reconnect ...real-time data started again on its own. This happened a few days ago too.
Excellent description of the situation ertrader, that was exactly what I experienced too. Where do you look to see the server if it's not the message shown above? I could not find the server listing you describe in my message log nor in any of the various server settings.
Same here... It is odd because during much more extreme market action later today, real-time data was keeping up just fine.
Yes, the same with me. But I must also inform that yesterday, 11/30/2022, upon the 8:45 and 9:00 EST releasings as well as at the time Jerome Powell spoke (13:30 EST) the Denali data feed was pretty stable despite the "heavy" volatility and volume conditions. I haven't changed anything in my system, my internet or whatsoever, as I don't have anything else left to change. I'm still hopeful that whatever the problem is, it will be definitely resolved soon. Date Time Of Last Edit: 2022-12-01 11:53:11
|
| [2022-12-02 00:17:36] |
| Sierra_Chart Engineering - Posts: 19872 |
|
Regarding post 11, this must be related to a server that was not able to be connected to. We have removed that server from the list. Restart Sierra Chart. We do watch the data feed, at the US Eastern time open at 9:30 AM. Here is a video for today for that time. See attachment below. There were no issues and this is what we have observed, consistently monitoring the last week. What we want to see in the log is if anyone was having a problem, when they are connected to DS21.SierraCharts.com. That uses an Internet connection from a different provider. However, we would not expect there to be any issue there either. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-12-02 00:18:17
|
 DenaliDataFeed Video_2022-12-01_093203.wmv - Attached On 2022-12-02 00:13:26 UTC - Size: 59.98 MB - 212 views |
| [2022-12-02 20:39:11] |
| User820791 - Posts: 15 |
|
Hey again. I've noticed that my sierra always connects to either of those 3 servers: ds21, ds23 or ds26 for data feed. Interestingly, when I try to ping each one I always get atleast 122ms latency. Is this the reason why my DOM feels very laggy? Please just be straight forward. Don't tell me to check your performance guides because I've gone through every single post very precisely. I wasted a huge amount of time trying to fix this problem. Date Time Of Last Edit: 2022-12-02 20:56:02
|
To post a message in this thread, you need to log in with your Sierra Chart account: