Support Board
Date/Time: Tue, 04 Feb 2025 07:55:29 +0000
Sub-instance data feed disconnect
View Count: 632
| [2020-01-09 17:27:51] |
| User907968 - Posts: 825 |
|
Hi, I am using this method for sharing data - https://www.sierrachart.com/index.php?page=doc/MultipleServices.html#AccessingMarketDataFromOtherInstancesOfSierra%20Chart My charts stopped for a brief period today, but gave no visible indication that there was a problem with the feed. Looking deeper, I find this message in the log of the sub-instance - Generic Client (127.0.0.1:11094) | Real-time data for symbol CLG0-NYMEX is currently unavailable. | 2020-01-09 11:03:10.986
And these messages in the server instance - DTC Client socket (6) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2020-01-09 11:03:10.984
DTC Client socket (6) | Socket gracefully closed by remote side. | 2020-01-09 11:03:10.984 DTC Client socket (6) | CloseSocket call. | 2020-01-09 11:03:10.984 DTC Client socket (6) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2020-01-09 11:03:10.984 DTC Client socket (6) | Closed. | 2020-01-09 11:03:10.984 DTC Client socket (0) | CloseSocket call. | 2020-01-09 11:03:10.985 SC Data - All Services | Disconnected from the server. | 2020-01-09 11:03:10.985 SC Data - All Services | Data feed disconnected. Will reconnect in 2 seconds. | 2020-01-09 11:03:10.985 SC Data - All Services | Using username 0 | 2020-01-09 11:03:12.995 SC Data - All Services | Connecting to the server ds7.sierracharts.com. Port 10048 | 2020-01-09 11:03:12.995 DTC Client socket (2) | Creating socket. | 2020-01-09 11:03:13.005 DTC Client socket (2) | Connecting to IP: 8.18.161.133. | 2020-01-09 11:03:13.005 DTC Client socket (2) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2020-01-09 11:03:34.054 DTC Client socket (2) | CloseSocket call. | 2020-01-09 11:03:34.054 DTC Client socket (2) | Closed. | 2020-01-09 11:03:34.054 DTC Client socket (0) | CloseSocket call. | 2020-01-09 11:03:34.054 SC Data - All Services | Disconnected from the server. | 2020-01-09 11:03:34.054 SC Data - All Services | Data feed disconnected. Will reconnect in 2 seconds. | 2020-01-09 11:03:34.054 I am not particulary concerned what the cause was, but I do have this question - Is there a way to setup a more overt warning when the above occurs? Date Time Of Last Edit: 2020-01-09 17:28:35
|
| [2020-01-10 00:59:49] |
| |
|
No there is not.
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 |
| [2020-01-10 11:31:58] |
| User907968 - Posts: 825 |
|
Ok, no worries. Instead, I made a study to check for data feed inactivity. If anyone wants the study, the code is attached. Date Time Of Last Edit: 2020-01-10 11:32:23
|
 InactivityAlert.cpp - Attached On 2020-01-10 11:31:27 UTC - Size: 4.41 KB - 309 views InactivityAlert_64.dll - Attached On 2020-01-10 11:31:39 UTC - Size: 126.5 KB - 357 views |
| [2020-01-11 20:31:10] |
| User379468 - Posts: 508 |
|
Shouldn't the main data feed connections status bar alert and change color to red on disconnect?
|
To post a message in this thread, you need to log in with your Sierra Chart account: