View Full Version : NT7 & MBT server connection loss and shut down
04-29-2010, 12:47 PM
I automate my forex trades using MBTrading and NT7. Throughout each day, there are several 1-3min. connection to server losses. (also happens at rollover) MBT claims it is not on their side.
These connection losses usually don't cause problems, HOWEVER if an order is triggered during these periods, the strategy will produce many alerts and eventually shut itself down. In response, I decided to add a safety stop loss to my strategies that would reside on MB's servers in the event the shut down occurs when I am away from my computer.
Problem: On two occasions, these shut downs have somehow managed to get the positions flat prior to shut down, but do not eliminate the stop. The forex stops are not "exit" orders, but either buy or sell. So my safety stop loss effectively becomes a residual net +/- order still on the MB servers after shut down. Any suggestions on what to do about this?
04-29-2010, 01:26 PM
Thank you for your post.
We received your email on this as well and will be following up with you there shortly.
05-25-2010, 10:18 AM
These connection losses usually don't cause problems
Hi billr. ┐Does it main that you dont have to restart your NT every day after the disconections??
This is new for me, since long time ago after the rollover time and their servers reboot NT6.5 crash totaly and dont reconect until reboot your NT.
Great to hear that.
05-25-2010, 10:33 AM
Yes. I am using NT7.15 (i think) w/MBT and the rollover and other temporary disconnections don't usually crash NT. However, if your strategy happens to attempt a trade during these periods, NT may force a shut down.
If you are experiencing the disconnects other than rollover, MBT has suggested opening a port in your router. ( I haven't tried that yet ).
You may also notice a lack of data for the previous 24 hours for a period of time. If you start a strategy or refresh your chart after about 10 mins after rollover, this seems to correct itself.
05-25-2010, 11:49 AM
BillR, Thanks very much, this┤s a very good new. At least sounds like they┤r doing some advances with the reconnections.
Could a Moderator confirm this? Thanks.
05-25-2010, 02:58 PM
Unfortunately I would not be able to confirm/deny MBT's suggestions on how they handle their rollovers. Please contact MBT directly to see what they say about those suggestions directly.
For strategies running during a disconnect, depending on your Connection Loss Handling settings in Tools>Options>Strategies>NinjaScript determines how the strategy will behave. If you have it set to KeepRunning it will keep running as if no disconnect happened up to the point where the strategy tries to trade again. If it tries to trade because you can't actually place the trade cause you are disconnected then the strategy will have no choice but to be forced to stop at that point in time.
05-26-2010, 06:08 AM
Thanks Josh. ┐ Is maight a posibility to insert a code in the strategy for "dont send any order if conection loss" ? Then we keep the strategy sleeping until it comes back and "Tools>Options>Strategies>NinjaScript.." will keep the strategy running..
Thanks very much.
05-26-2010, 06:47 AM
syscali, to a limited degree you could work with OnConnectionStatus() in your strategy - http://www.ninjatrader.com/support/helpGuides/nt7/onconnectionstatus.htm
09-15-2010, 05:00 AM
Is anyone else seeing this behavior?
I am running beta 21 with the Ninja recomended version of MBT Navigator on Windows 7 x64. I have observed for three days running that Ninja will crash at approximately 0637 eastern time. I can see through the grayed out crash screen that the MBT connection status in the Ninja control center has changed to orange from the normal green.
This is a tremendous improvement over beta 20 where Ninja would crash many times a day seemingly every single time MBT servers or my Internet connection had a hiccup.
These crashes did not occur until version 20 as far as I can tell but I was not a daily user of 18 and 19.
Does anyone else have a clearer picture of this problem?
As an experiment I left an older version (17) running under XP in a virtual machine on this same Win 7 x64 machine, no crashes of it but other slow data loading issues plague it.
I will update the VM XP Ninja to 21 soon and test it.
UPDATE: I just updated my XP version of Ninja and logged into MBT while still logged in under my Win 7 Ninja. It seems the Win 7 Ninja crashed immediately when MBT was giving the message that I had logged in elsewhere. So perhaps support can replicate the crash on demand with this technique if you need to.
UPDATE 2: Ninja has now been running on my XP virtual machine under Windows 7 x64 for over three days with no crashes. I guess the crashing has something to do with MBT and Ninja 32 bit apps running under Win 7 x64 but who knows... the good thing is Ninja with MBT is apparently totally stable under the VM XP and that is perfect for my uses.