Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 26 Apr 2024 18:26:16 +0000
Keep getting disconnected - not sure what it is - PLEASE HELP
View Count: 977
| [2018-01-05 21:09:17] |
| User299392 - Posts: 216 |
|
See log below - Socket (1012) | Socket gracefully closed by remote side. | 2018-01-05 16:06:20 Socket (1012) | Closed. | 2018-01-05 16:06:20 Chart #5 has tagged chart #10 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Chart #5 has tagged chart #11 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Chart #5 has tagged chart #12 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Chart #5 has tagged chart #2 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Chart #5 has tagged chart #3 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 F.US.ENQH18 [CB] Flex Renko 5-4-0 #12 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 F.US.ENQH18 [CB] Flex Renko 8-5-3 #11 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Opened cached Intraday file: C:\SierraChart\Data\UDVR-NASDAQ.scid | 2018-01-05 16:06:20 F.US.ENQH18 [CB] 233 Trades #10 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 Opened cached Intraday file: C:\SierraChart\Data\F.US.ENQH18.scid | 2018-01-05 16:06:20 Chart #4 has tagged chart #10 for full recalculation. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:20 F.US.ENQH18 [CB] Flex Renko 21-13-20 #3 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:55 F.US.ENQH18 [CB] Flex Renko 34-13-0 #2 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:55 CQG WebSocket | Timeout waiting for pong message from server. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Adding bytes from final send buffer from buffered socket: 8 | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Initiating close of socket by core. | 2018-01-05 16:06:55 CQG WebSocket | WebSocket closed. | 2018-01-05 16:06:55 CQG FIX Trading | WebSocket closed. | 2018-01-05 16:06:55 Connection to the external service has been lost. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Write in progress. Shutdown being delayed. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Sending bytes from final send buffer: 8 | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Write has completed. Shutdown being performed. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Shutdown started. Waiting for graceful close. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Socket gracefully closed by remote side. | 2018-01-05 16:06:55 CQG WebSocket socket (1009) | Closed. | 2018-01-05 16:06:55 F.US.ENQH18 [CB] 233 Trades #10 | Performing a full recalculation because it has been tagged. Chartbook: Testing-3TimeLines.Cht | 2018-01-05 16:06:55 CQG FIX: DisconnectFIX called. | 2018-01-05 16:06:58 CQG FIX: Sending a Logout message. | 2018-01-05 16:06:58 DTC Client socket (1010) | Initiating close of socket by core. | 2018-01-05 16:06:58 SC DTC Data with Market Depth | Disconnected from the server. | 2018-01-05 16:06:58 DTC Client socket (1010) | Shutdown started. Waiting for graceful close. | 2018-01-05 16:06:58 CQG FIX Trading | Disconnected. | 2018-01-05 16:06:58 DTC Client socket (1010) | Socket gracefully closed by remote side. | 2018-01-05 16:06:58 DTC Client socket (1010) | Closed. | 2018-01-05 16:06:58 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2018-01-05 16:06:58 CQG FIX socket (1008) | Initiating close of socket by core. | 2018-01-05 16:06:58 CQG FIX: Disconnected. | 2018-01-05 16:06:58 CQG FIX socket (1008) | Shutdown started. Waiting for graceful close. | 2018-01-05 16:06:58 CQG FIX socket (1008) | Socket gracefully closed by remote side. | 2018-01-05 16:06:58 CQG FIX socket (1008) | Closed. | 2018-01-05 16:06:58 |
| [2018-01-05 21:53:18] |
| |
|
CQG has been contacted about this. From our side there is absolutely nothing we can do other than report the problem to them. This is for them to take care of. And we really are not happy when CQG is charging us $500 a month now, which we are just absorbing and then there are all of these connectivity problems. 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: 2018-01-05 21:53:45
|
| [2018-02-02 15:29:34] |
| User299392 - Posts: 216 |
|
Hi - Just checking. Was this problem ever fixed by Sierra or CQG? It still persists for me. Do you recommend creating new chart books? |
| [2018-02-02 17:28:45] |
| |
|
There is no problem on the Sierra Chart side. This is the information we have about this: CQG Trading Platform Service: Frequent Server Disconnections when Using CQG You would not need to do anything with your Chartbooks unless they are creating high CPU usage, and therefore freezing Sierra Chart for an extended time. In this case, refer to help topic 30: Http://www.sierrachart.com/index.php?page=doc/helpdetails30.html 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: 2018-02-07 00:54:15
|
To post a message in this thread, you need to log in with your Sierra Chart account: