Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 03 May 2024 20:46:09 +0000
Post From: Data Feed freezing
| [2020-06-06 13:49:06] |
| |
|
In regards to post #3, you said : Below is the log from this morning when I first signed in to the time I had to disconnect and reconnect my connection to get it to work
But the log does not show that you disconnected, we can tell that clearly. There is no manual disconnection logged anywhere. Instead it shows: DTC Client socket (2) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2020-06-04 10:01:05.977 *
DTC Client socket (2) | Socket gracefully closed by remote side. | 2020-06-04 10:01:05.977 And this is what the server shows: 2020-06-04 14:00:42 | Client connection (183) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine.
So this indicates a network connectivity issue. The interesting thing the timing difference here does indicate really a complete loss of connectivity. So this does not indicate a server problem but a user specific issue involving network connectivity. You need to disregard the hours part of the time and only look at the minutes and seconds. Notice how the server closed the connection ahead of your side detecting a problem. This is simply an issue with the public Internet connectivity.2020-06-04 14:00:42 | Client connection (183) | Socket gracefully closed by remote side. Regarding post #5, there is nothing in the log which helps us identify the issue and we are adding additional logging into our server process. So at this point we want you to let us know when you notice it again and we will have the additional logging in place. Then we will take it from there. Also for the record we have never noticed an interruption with the data feed when monitoring on the other side of the world. And this is monitoring it at the busiest times. And in the past, when we have heard of reports of this, we have definitely determined that the issue is due to a network connectivity problem. And we also have an abundant of problems with CQG users with connectivity problems. Far far in excess of what we have with our Denali data feed which at most is just two or three users affected. And no indication that this is a server issue. And in each case, whether there is a problem With CQG, or the Denali feed, these are external network issues. With the public Internet, anything can go wrong. We also noticed that you are in California and we are going to be setting up infrastructure on the West Coast of the US that we can use to forward the data and maybe that will help. 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-06-06 16:23:35
|