Support Board
Date/Time: Tue, 14 Jan 2025 23:42:34 +0000
Post From: SC Disconnecting from CQG throughout the day - started with v 1369
| [2016-02-18 01:58:27] |
| |
|
These are the relevant passages: CQG WebAPI websocket (45) | Closed. No error. | 2016-02-17 10:30:19 CQG WebAPI websocket (45) | SSL shutdown indicates not able to send 'close notify'. | 2016-02-17 10:30:19 CQG WebAPI websocket (45) | SSL has been shut down. | 2016-02-17 10:30:19 CQG WebAPI websocket (45) | SSL object has been freed. SSL state is now disconnected. | 2016-02-17 10:30:19 CQG WebAPI websocket (45) | Shutdown and closed. | 2016-02-17 10:30:19 CQG WebAPI | Network socket for websocket has been closed by remote side. | 2016-02-17 10:30:19 This is not an issue with any specific Sierra Chart version. It could not be. The Message Log makes that clear. Refer to: CQG Trading Platform Service: Solving CQG Market Data Feed Problems This kind of problem has been reported quite a lot in the last month or so. By other users as well. And with earlier versions as well. It is not specific to any particular version. The other program using CQG is not likely using the Web API. Otherwise it would be affected as well. The problem is with the CQG Web API. There is nothing we can do about this. Although CQG did add a new parameter to their web API that will be released in the next version of Sierra Chart which might help with something like this, but we think really it is an improper fix and will not deal with the underlying problem. So at this point we are losing confidence in the CQG system over this. 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-18 02:00:37
|