Support Board
Date/Time: Sun, 08 Sep 2024 00:28:17 +0000
Rithmic/APEX Data Lag
View Count: 831
[2024-07-09 17:14:47] |
John - SC Support - Posts: 34254 |
You are having problems with your Rithmic connection, which will cause issues with the data as well, as the connections to your trading service and the Denali data are tied together (i.e. if you lose connection to your trading service, your data will also stop until the connection is restored). In particular, we see the following in the log: DTC Client socket (5) | 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.
Rithmic Direct - DTC | There has been no activity on the network socket for 45s. Will reconnect.
| Connection to the external service has been lost. | Rithmic Direct - DTC | Waiting for socket receive thread to end | DTC Client socket (2) | CloseSocket call. | DTC Client socket (2) | Max send buffers used during socket life: 3 | DTC Client socket (2) | Max send buffer size during socket life: 442 | DTC Client socket (2) | Shutdown started. Waiting for graceful close. | Rithmic Direct - DTC | Disconnected. Our only suggestion is to try a different Rithmic server. There is nothing we can do from our end for this, as it is a Rithmic issue. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
[2024-07-09 17:35:08] |
User753526 - Posts: 46 |
Ok thanks. Sounds like it is these ongoing issues with Rithmic lately. I'll try a few different Rithmic servers as you suggest.
|
To post a message in this thread, you need to log in with your Sierra Chart account: