Support Board
Date/Time: Sat, 10 May 2025 16:26:03 +0000
Post From: Frequent disconnect from CQG
| [2016-02-04 03:56:57] |
| |
|
We are releasing Sierra Chart version 1365 now which supports server-side OCO (Order Cancels Order) when using the CQG Web API. This is from CQG relating to the CQG Web API disconnections: Disconnections #3 and #4 (with sessionToken "vyP2jtJjkyZ9gebKzexyjVGeyObec+d1mZGLoqjnDWc" and "9880Z6ijKH7KZpy3uNAzXIKexLoGN4UcDKZg4BzSXR0" correspondingly) happened because of exceeding real-time market data delay: it reached more than 15 seconds. Most probably it related with client-side connection problems. Disconnections #1 and #2 (with sessionToken "Jai4Ss/8XaOYQ6VlZ7H0K6a5UsuArQuzmYxtIvHLm7U" and "bCqPBIdHvAMCKQXfJmt/WbbtQbyfOeIMVN1zLJnc9OE" correspondingly) are more tricky. In both cases I didn't saw nothing serious except of some unknown warnings from websocket library. Looks like in these cases WebAPI didn't disconnect user connections, user sessions were deleted after 'Logoff' message from client. I also saw some unknown warnings like "websocketpp [error]: Timer Expired" and they also look like a client-side problems, but I'm not sure that these problems related with SierraCharts users (I have no way to get IP-addresses or session tokens of connections that leaded to these messages). 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 |