Support Board
Date/Time: Tue, 26 Nov 2024 06:49:28 +0000
DTC Server not sending Heartbeat message on agreed time interval
View Count: 346
[2024-01-02 01:17:27] |
User218244 - Posts: 21 |
The HeartbeatIntervalInSeconds field of the LogonRequest message is set to 5, however the DTC Server is only sending a Heartbeat message approximately every 10 seconds. This is causing an intermittent failure in my DTC Client since I am expecting a Heartbeat message at most every 2*5=10 seconds, as recommended in the documentation. The following selection is in the Sierra Chart message log, so the DTC Server is properly receiving the Heartbeat interval time, but not using it: 2024-01-02 00:56:21.674 | DTC client #1. 127.0.0.1 | Requested heartbeat interval: 5
I have just upgraded to the current version of Sierra Chart (2576) and this issue did not occur with the earlier version I was using. |
[2024-01-02 05:18:18] |
Sierra_Chart Engineering - Posts: 17179 |
This is because for efficiency, there is a single timer which drives the heartbeat messages. So it is not possible for a client connection to increase the rate of the heartbeat. Just work with a 10 second heartbeat. There is no possibility of us changing this under any circumstances. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
[2024-01-02 13:13:15] |
User218244 - Posts: 21 |
Ok, I have modified my DTC Client application with this change in behavior. The relevant DTC Protocol documentation (e.g. from Authentication and Connection Monitoring Messages) does not indicate that Sierra Chart now only supports a 10 second heartbeat interval: [int32] HeartbeatIntervalInSeconds ... This should be a value from anywhere from 5 to 60 seconds. ...
|
To post a message in this thread, you need to log in with your Sierra Chart account: