Support Board
Date/Time: Wed, 27 Nov 2024 04:57:46 +0000
Post From: CTS disconnections
| [2014-07-15 23:36:48] |
| |
|
It is completely normal for connections to fix-chart.t4login.com which is used for historical chart data to be closed on the CTS side after 30 seconds of inactivity. That connection is not used for real-time data. Any log entries on either side for historical chart data, are not relevant to the problem. In your particular case, one reason why Sierra Chart would log off the chart data connection on its own is if the main connection use for trading and real-time data, gets disconnected, then chart data connection will be disconnected as well. But this is only a side effect and not relevant to the main issue. "dropped sockets" is an imprecise term. The only proper terminology would be the actual specific socket errors that occur. Based upon your logs, there are plenty of cases, where the connection is clearly getting closed on the remote side and for those connections we need to know the reason why. The most relevant way to track this down, is to find out why the server stops sending the data when you see this in the Sierra Chart log: The data feed was lost. There was no activity for at least
That must be the focus. In the minutes around that message, why is the server not sending 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: 2014-07-15 23:39:13
|