Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 27 Apr 2024 18:28:01 +0000
Post From: How to disable orders being resubmitted
| [2019-01-15 18:03:05] |
| |
|
We want you know that we have spent a fair amount of time looking into this and the only potential of a resend of an order would be at the HTTP level and the most that potentially could occur would be a single retry. There is clear safety mechanisms in place to prevent anything further and that retry only occurs on a lost socket connection with no acknowledgment from the remote side. And this relates to pipelining support where a retry would be necessary in the event that the server does not support pipelining. And that retry would only be on a new connection to the server. The problem is your log above does not show any reconnection to BitMex at the time so at this point this does not appear to have been an issue on the Sierra Chart side. We have heard about an issue like this one time before from someone in Russia and based upon what we are seeing here, we see no evidence that this was a problem at all on our side. And that is what we thought at the time as well. Nevertheless we are still going to make some lower level changes to ensure there is no possibility whatsoever of even a single retry and we are going to remove support for HTTP pipelining because that whole concept is flawed to begin with. We have read that modern web browsers no longer have that enabled. 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: 2019-01-15 18:06:31
|