Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Tue, 21 May 2024 17:37:00 +0000
Post From: SC Disconnecting from CQG throughout the day - started with v 1369
| [2016-02-19 17:38:38] |
| |
|
The bolded part indicates that CQG is closing the connection: 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 CQG FIX Trading | Websocket closed. | 2016-02-17 10:30:19 Therefore, when this happens give us the entire Message Log and we mean the entire Message Log and then we will ask CQG why they are closing the connection. If Sierra Chart is doing something improper on the web socket connection which is causing a remote close, we need to know what that is. 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 |