Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 18 May 2024 15:00:50 +0000
Post From: Post your pathping route to TransAct Futures server
| [2015-11-01 10:06:17] |
| |
|
Long story short, my connection to the brokerage would die right after the parent order gets filled, and when I log back in, the attached child orders (stop and target) were nowhere to be found. We worked with my ISP and made some route adjustment due to packet losses at 2 of the hops, and we will see this fixes the problem.
Another problem that is also happening is that the TransAct bridge program was abnormally shutting down when the TransAct server closed the connection when it did not get a response back from the TransAct API after about a second, when an order fill was sent to it. TransAct needs to solve the problem with the bridge program. And also it is our position that the trading server should be much more tolerant than about a second when waiting for a client-side acknowledgment. More like 10 seconds. Trading connections we use with other trading services will only timeout after about 40 seconds and do not require acknowledgment of fills from the client-side. Only the underlying TCP protocol is relied upon to ensure the packets make it through. Perhaps the timeout should be tighter for trading, but this is what we normally use since the connection may also carry market data. The IP address of the TransAct server 208.97.219.185 is in Chicago. Use this tool here to check that: http://www.ip2location.com/demo It is possible that the actual location of 62.216.147.66 is being misidentified. Also in one of your email messages you were saying that you were going to reinstall the TransAct software and Sierra Chart. There is no need to reinstall these programs. The problem is not going to be changed by reinstalling these programs. Here is a trace we ran to the TransAct server: 3 6 ms 6 ms 6 ms ten-2-1-0-350.bdr01.alb01.akl.VOCUS.net.nz [175.
45.102.137] 4 133 ms 132 ms 132 ms ten-0-1-0-2.cor01.alb01.akl.VOCUS.net.nz [114.31 .202.38] 5 131 ms 132 ms 132 ms bundle-200.cor01.lax01.ca.VOCUS.net [114.31.202. 45] 6 134 ms 133 ms 133 ms bundle-101.bdr01.lax01.ca.VOCUS.net [114.31.199. 61] 7 131 ms 132 ms 132 ms te0-2-0-2.rcr21.lax04.atlas.cogentco.com [38.88. 197.109] 8 134 ms 134 ms 133 ms be2017.ccr22.lax01.atlas.cogentco.com [154.54.0. 238] 9 168 ms 168 ms 168 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7. 53] 10 174 ms 173 ms 173 ms be2443.ccr22.dfw01.atlas.cogentco.com [154.54.44 .230] 11 183 ms 183 ms 183 ms be2433.ccr22.mci01.atlas.cogentco.com [154.54.3. 214] 12 194 ms 195 ms 195 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6. 118] 13 195 ms 194 ms 195 ms be2217.ccr41.ord03.atlas.cogentco.com [154.54.24 .206] 14 195 ms 195 ms 195 ms te0-0-2-0.agr11.ord03.atlas.cogentco.com [154.54 .0.54] 15 194 ms 193 ms 194 ms 38.88.204.38 16 194 ms 194 ms 194 ms gatekeeper.yorkba.com [208.97.219.185] 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: 2015-11-01 10:13:37
|