IB: Adapter activly refused

[zweistein]

Hello to the Ninja Team and good morning,



I continue to have connection problems with IB in certain cases and I get the infamous message IB: No connection could be made because the target machine actively refused it.
There are numerous posts concerning this message!


I have traced down the problem and I quite firmly believe that this is a bug of the Ninja IB adapter.

Here my findings:

The content of the message makes sense: It means that TWS is already connected to Ninja and therefore a second connection is refused.

Can TWS already be connected to TWS? Yes it can and the typical case is that you have two or more IB accounts and one of them is already connected.
The IB adapter will then - erroneosly - take the running instance of TWS for good and will try to connect. But it will fail since the other IB connection is already there.

Here a fix proposal for your software guys:

Please check - when you get that message or always- wether there is another TWS connection already made in case you find the TWS application running. If you find another IB connection open then please load a new TWS instance instead and connect to the new TWS instance.

for example (pseudo-code)

ConnectToTWSAdapter(){

List<Connection> connections=FindAllActiveConnections();
List<TWSInstance> twsInstances = FindAllRunningIstances(TWS);
List<TWSInstance> twsAvailable=new List<TWSInstance>(twsInstances);
// create a copy to work on

foreach(Connection c in connections){

if c.Adapter==IB && c.IsConnected) {
twsavailable.Remove(c.twsInstance);
}

}

TWSInstance useMeTWS=null;
if(twsAvailable.Count>0) useMeTWS=twsAvailable[0];

if(useMeTWS==null) {
useMeTWS=LoadNewTWSInstance()
}

connectToInstance(useMeTWS);
}


I would welcome if your developers could revise the IB adapter logic and hopefully the above suggestions are useful and appreciated.

Best regards
Andreas

[NinjaTrader_Dierk]

>> The IB adapter will then - erroneosly - take the running instance of TWS for good and will try to connect.
This is not an error but works as expected: NT will try to connect to a running TWS instance.

[zweistein]

Yes, but your approach is a bit simplistic:

You must differenciate the tws running instances between running tws instrances already connected and those not connected.
For a new connection you must use a running TWS instance not yet connected.


Otherwise your error will always show up when you try to connect automatically to a second IB . Current solution is to load the second TWS manually.
Remember that you offer MultiBroker licenses and I expect you to have your logic revised for this.

Best regards

[NinjaTrader_Dierk]

Thanks for your suggestion. We'll add it to the list of future considerations.

[shakeham]

Originally Posted by NinjaTrader_Dierk

>> The IB adapter will then - erroneosly - take the running instance of TWS for good and will try to connect.
This is not an error but works as expected: NT will try to connect to a running TWS instance.

Dear Admin, I also have the same problem of connecting to IB. actively refused by IB TWS. It keeps saying that every single time no matter I have TWS running or not. Does anyone actually has NinjaTrader working with latest TWS?
Thanks

[NinjaTrader_RJ]

Originally Posted by shakeham

Dear Admin, I also have the same problem of connecting to IB. actively refused by IB TWS. It keeps saying that every single time no matter I have TWS running or not. Does anyone actually has NinjaTrader working with latest TWS?
Thanks

Hello,

Thank you for your post.

The "latest TWS" is NOT supported by NinjaTrader 6.5. Please downgrade to TWS 892.7 from here: http://www.ninjatrader.com/webnew/su...ivebrokers.htm

[NinjaTrader_RJ]

Originally Posted by shakeham

Dear Admin, I also have the same problem of connecting to IB. actively refused by IB TWS. It keeps saying that every single time no matter I have TWS running or not. Does anyone actually has NinjaTrader working with latest TWS?
Thanks

Please make sure you have followed each step in the connection guide from my last post as the error you received indicates some steps were missed.

Thank you!