Support Board
Date/Time: Tue, 13 May 2025 10:01:55 +0000
CQG weekend data disconnect
View Count: 94
| [2025-04-28 00:45:14] |
| User745789 - Posts: 377 |
|
I know you do not support CQG, but I wonder if there is a way for SC to handle the regular CQG weekend data disconnects. Early Saturday I always get a SC pop-up window saying that CQG data has been disconnected. I need to click ok on that pop-up, then reconnect my data feed ready for Monday's trading. Is there any way to automate this? I have Global Setting >> Reconnect on Failure set to yes, but that deals with a different situation.
|
| [2025-04-28 14:39:55] |
| Sierra_Chart Engineering - Posts: 19571 |
|
At the time of the disconnection we need to see the Message Log and see the reason for the disconnection and why there is not an automatic reconnection. Instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We only need to see the last 20 or 30 lines. Just where the disconnection occurs. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-04-28 23:43:02] |
| User745789 - Posts: 377 |
|
Thank you. Here is the last block of messages on Saturday morning when the disconnection occurred. The next messages were Monday morning. I have to manually close the SC pop-up (regarding CQG disconnect) and manually reconnect data to start trading again. Disconnect happens every Saturday morning. 2025-04-26 08:31:05.281 | CQG WebAPI | Connecting to server api.cqg.com 2025-04-26 08:31:05.281 | CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 2025-04-26 08:31:05.290 | CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. 2025-04-26 08:31:05.290 | CQG WebSocket socket (1) | New receive buffer size: 0 2025-04-26 08:31:05.290 | CQG WebSocket socket (1) | Connecting to IP: 118.201.11.220. 2025-04-26 08:31:05.294 | CQG WebSocket | Opening WebSocket. 2025-04-26 08:31:05.294 | CQG WebSocket | Sending WebSocket handshake. 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | Connection: Upgrade 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | Sec-WebSocket-Accept: kaADavd3Jh7qJ32c+IfnTT0kgzI= 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | Server: WebSocket++/0.8.2 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | Upgrade: websocket 2025-04-26 08:31:05.308 | CQG WebSocket | Server header | 2025-04-26 08:31:05.308 | CQG WebSocket | Web socket state is now open. 2025-04-26 08:31:05.308 | CQG WebAPI | WebSocket connected. 2025-04-26 08:31:05.308 | CQG WebAPI | Sending market data logon message. 2025-04-26 08:31:05.317 | CQG WebAPI | Logon unsuccessful. Server message: Trade routing is not available now. Contact customer support for assistance. 2025-04-26 08:31:05.318 | CQG WebSocket socket (1) | CloseSocket call. 2025-04-26 08:31:05.318 | CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. PendingSize=0 2025-04-26 08:31:05.318 | Denali Data Feed | Waiting for socket receive thread to end 2025-04-26 08:31:05.319 | DTC Client socket (2) | CloseSocket call. 2025-04-26 08:31:05.319 | DTC Client socket (2) | Shutdown started. Waiting for graceful close. 2025-04-26 08:31:05.319 | Denali Data Feed | Disconnected from the server. 2025-04-26 08:31:05.319 | CQG WebAPI | Disconnected. 2025-04-26 08:31:05.319 | CQG WebAPI | Not reconnecting due to connection error condition. 2025-04-26 08:31:05.319 | CQG WebSocket | WebSocket closed. 2025-04-26 08:31:05.319 | CQG WebAPI | WebSocket closed. 2025-04-26 08:31:05.321 | CQG WebSocket socket (1) | Write has completed. Shutdown being performed. 2025-04-26 08:31:05.322 | CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. 2025-04-26 08:31:05.325 | CQG WebSocket socket (1) | Socket gracefully closed by remote side. 2025-04-26 08:31:05.325 | CQG WebSocket socket (1) | Closed. 2025-04-26 08:31:05.533 | DTC Client socket (2) | Socket gracefully closed by remote side. 2025-04-26 08:31:05.534 | DTC Client socket (2) | Closed. |
| [2025-05-06 15:35:22] |
| Sierra_Chart Engineering - Posts: 19571 |
|
We are adding more logging to see the best way to solve this. But there really is not a good solution. CQG is just simply disconnecting and there is not going to be an opportunity to reconnect, for an extended time.
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, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: