Support Board
Date/Time: Wed, 05 Feb 2025 14:06:42 +0000
Disconnections AMP/CQG
View Count: 1211
| [2014-12-05 15:06:26] |
| User11942 - Posts: 298 |
|
Hi SC team, I've been experiencing multiple re-connections to AMP CQG service since 8:30 AM EST today and it keeps going. It has happened more than 10 times now(!!!). The problem appeared first this Monday once I updated to ver.1214. (Before that everything was OK, but it may be coincidence though). I see the same error message in the log every time a disconnection occurs. Websocket | Received opcode Close. Received status code: 65536000 | 2014-12-05 09:47:00
Is this a problem of SC? Or shall I contact AMP/CQG about that? Or should I blame my ISP? Please let me know the reason of disconnections. I attached entire log herein. There are no lost packets and tracing doesn't return errors. Thank you.
CQG FIX Trading | Websocket closed. | 2014-12-05 09:47:00 Connection to the external service has been lost. | 2014-12-05 09:47:00 CQG FIX Trading FIX: Sending a Logout message. | 2014-12-05 09:47:00 Sending logoff message. | 2014-12-05 09:47:00 Socket (1912) | SSL shutdown indicates not able to send 'close notify'. | 2014-12-05 09:47:00 Socket (1912) | SSL has been shut down. | 2014-12-05 09:47:00 Socket (1912) | SSL object has been freed. SSL state is now disconnected. | 2014-12-05 09:47:00 Socket (1912) | Shutdown and closed. | 2014-12-05 09:47:00 CQG FIX Trading | Websocket closed. | 2014-12-05 09:47:00 CQG FIX Trading | Disconnected. | 2014-12-05 09:47:00 Will reconnect to the server in 5.0 seconds Select 'File >> Disconnect' to prevent further connection attempts. | 2014-12-05 09:47:00 CQG FIX Trading FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2014-12-05 09:47:01 socket (2172) | Shutdown and closed. | 2014-12-05 09:47:01 CQG FIX Trading FIX: Logged out and disconnected. | 2014-12-05 09:47:01 CQG FIX Trading FIX: Disconnected. | 2014-12-05 09:47:01 Date Time Of Last Edit: 2014-12-05 15:27:18
|
Private File |
| [2014-12-05 18:33:29] |
| |
|
This means that the CQG server intentionally closed the connection: Websocket | Received opcode Close. Received status code: 65536000 | 2014-12-05 09:47:00 Based upon what we have heard from CQG, this indicates a problem where the network connection is not able to handle the amount of data being sent. 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 |
| [2014-12-05 19:08:29] |
| User11942 - Posts: 298 |
|
a problem where the network connection is not able to handle the amount of data being sent.
Thank you for the info.That sounds quite reasonable considering today's flows of data. Would it mean bandwidth or latency or general connection issues? I just read other thread with the same problem described where you mentioned possible fix by flagging overloads to CQG. Was that implemented? Does ver.1214 have that fix? |
| [2014-12-05 19:12:51] |
| |
|
Would it mean bandwidth or latency or general connection issues?
We do not know. It is not possible for us to know. CQG might be able to give you a better answer.In the latest Sierra Chart version, there is a CQG specific option: Global Settings >> Data/Trade Service Settings >> Allow Server to Drop Data 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: 2014-12-05 19:13:31
|
| [2014-12-05 19:16:47] |
| User11942 - Posts: 298 |
|
Thanks. NVM. I think I discovered a root of the problem.
|
To post a message in this thread, you need to log in with your Sierra Chart account: