Support Board
Date/Time: Wed, 15 Jan 2025 00:07:09 +0000
Post From: SC Disconnecting from CQG throughout the day - started with v 1369
| [2016-02-22 21:51:44] |
| |
|
Here is the information from CQG about the disconnection reported by Yoda: 02/19/2016 14:46:58.247
Heartbeat: Send ping request. Ping time 20160219T144658.247042. 02/19/2016 14:46:58.247 Message out: ping { token: "WebAPI Server Heartbeat" ping_utc_time: 429184247 } 02/19/2016 14:46:58.829 Message in: pong { token: "WebAPI Server Heartbeat" ping_utc_time: 429184247 pong_utc_time: 429159083 } 02/19/2016 14:46:58.829 Heartbeat: Pong received. Durations: ping -25164 ms, pong 25746 ms, roundtrip 582 ms. 02/19/2016 14:47:28.831 Heartbeat: Send ping request. Ping time 20160219T144728.831692. 02/19/2016 14:47:32.938 Real-time data delay exceeds threshold. Disconnecting user session See how we never send out the last ping, there is no “message out:”. We keep working on it. I think we’ve helped reduce but not eliminate the disconnects. So apparently they are disconnecting because the computer's clock is not set accurately. If the other program is not having a problem with this, then maybe it is independently keeping track of the time since connection and not using the computer clock. This can get kind of elaborate for something that should not be complicated to begin with. They should never be disconnecting based upon the timestamps in a pong. 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: 2016-02-22 21:57:40
|