Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I understand and agree that would be very frustrating. Hopefully our public discussion will prod our friends at Ninjatrader a bit. Best of luck to you with your present situation.
Be yourself; everyone else is already taken. Oscar Wilde
We are in final testing of this release now. This change by no means is guaranteed to resolve anyone having disconnect issues but it may help. They current disconnect sensitivity has been in production use by thousands of users on a daily basis for many years. This change is not a fix but an improvement to try and capture the fringe cases where users internet connection is momentarily unstable. I just thought I would mention it in this thread since I thought it relevant.
@NinjaTrader thanks for the reply. So is final testing a few weeks or could it be a few days? I was told a few weeks ago r22 would be out in a few weeks which would be this week. I know there are other things this is slated to fix outside of CQG as well.
"The day I became a winning trader was the day it became boring. Daily losses no longer bother me and daily wins no longer excited me. Took years of pain and busting a few accounts before finally got my mind right. I survived the darkness within and now just chillax and let my black box do the work."
@NinjaTrader - Thank you for taking time to update us here with your progress on this issue. It seems odd some users are consistently experiencing disconnects, while other users never have disconnects. You mention the fringe cases of some users with momentarily unstable connections. Some of us here are speculating the tracert through the servers / internet may be a cause. Which leads me to postulate the concept that some connections are being dropped midway through the server tracert. Suggesting a connection sensitivity issue, but if that is the case how is it that some users with many hops across the continent have no disconnects, whereas users in the Aurora Data Center with virtually no hops or latency are experiencing disconnects ? Perhaps you can provide us with a general high level concept of what is happening ?
You may want to also consider addressing the same issue with Rithmic in your R22. I have just stopped repeated reporting of frequent disconnect and freezing with Ruthmic. Dorman's response to this issue is basically reprinting of whatever your support tells them about the issue.
@trendwaves I am not sure if the two are related. I think the disconnect issue is NT related. But the latency issue has to do with routes to CQG servers. I am not in Aurora but am in Chicago datacenter. I had my provider look into it and there is problem with last two hops to the CQG server. It has to do with route but I have no idea whose fault it is. I tried to get them to reroute but they did not think would help since it is in such close proximity to the destination. This is what they told me
" I personally have observed a lot of packet loss and latency issues with many different carriers (i.e, Verizon, Level 3, Savvis, Centurylink, ATT and Cogent) over the past two months which have effected many services to a wide range of clients, either local, in different parts of the US and even international. Even if a route changed, we have zero visiblity as far as the configurations, physical infrastructure of said carriers. A route change would likely put the traffic in yet another unpredictable latency/packet loss situation. The traffic will always try to find a route, which may vary, due to the overall designs of peering between the tier 1 carriers.
"
I am actually considering trying to locate in the Aurora center to cut out some hops. Because seems problem is with the carriers in regards to latency.
"The day I became a winning trader was the day it became boring. Daily losses no longer bother me and daily wins no longer excited me. Took years of pain and busting a few accounts before finally got my mind right. I survived the darkness within and now just chillax and let my black box do the work."
Lot's of questions so I will boil the answers down:
- Relative to CQG/Continuum, I can't speak to more specifics on their API relative to connections, this is a question for their developers. Historically we triggered a disconnect when CQG API reported a slow connection state. We have changed this with R22 to keep ignore this state and not report a lost connection. We are comfortable in doing this since in our testing, slow connection state seems to be infrequent and temporary.
- Rithmic, there is no issue that NinjaTrader can address. The Rithmic API controls the connection state, we simply pass through the information
- R22 was targeted to be released by the end of this week. If our testing goes well, that could still be the case. I simply stated a few more weeks in the case that we run into an unexpected issue.
I have two connections, on startup i automatically open IQ feed for my data feed and manually i open continuum for my broker connection (mirus/dorman). I have no disconnects on IQ feed, but the continuum connection very regularly drops and is unable to reconnect (for example now 25/2 8:50 Brussels time).
So the problem is not my internet connection.
It might be the international routing towards the continuum server(s) that is experiencing problems for some users like me ?
