NTClosePosition() bug?

[clearpicks]

If you really decide not to support trading multiple TWS accounts, please at least keep some basic things unbroken in the future release (I mean at least allow EFS to send out and cancel (OCO) orders and close positions via NT DLL). I don't use those NT DLL functions such as modifying orders, retrieving P/L, etc.

If that error message is generated by NT or NT DLL, as a simple workaround, could you conside to add a flag in NT or NT DLL to disable the popping out of error 135 message window? Right now everything works fine except this annoying error 135 message window.

- Clearpicks

[NinjaTrader_Ray]

In post #9 you told me this pops up with only one TWS connected which is why I tested. In any case, we will not disable the ability to establish multiple connections, we just don't support it at this time which could cause the messages you see.

[clearpicks]

Hello Ray,

I am glad to know multiple account trading would still be working in the future.

Even if with only one IB TWS account is connect, sometimes it still pops out. Especially when entering two oposite positions so that there is no contracts in the account but two OCO order pairs. In this case, an error message always pops out if you try to cancel them at the same time usign NTCancelAllOrders() as described in this thead http://www.ninjatrader-support.com/v...ead.php?t=7909

So it seems the problem is not in how many accounts are connected, but in how many OCO order pairs being cancelled.

Maybe adding a flag to suppress this error 135 message is a simple yet working workaround. How do you think?

- Clearpicks

In post #9 you told me this pops up with only one TWS connected which is why I tested. In any case, we will not disable the ability to establish multiple connections, we just don't support it at this time which could cause the messages you see.

[NinjaTrader_Ray]

Thanks for the suggestion, will consider it for the future.

[clearpicks]

Hello,

Is there any chance to disable the showing of error 135 message in the next NT update which is due in next a few weeks? Thanks

- Clearpicks

[NinjaTrader_Ray]

No there will not be.

[clearpicks]

Too bad. It seems I have to wait for quite some time.

Is it a NT DLL issue or NT native issue? When using NT ChartTrader or DOM, when cancelling multiple OCO pairs, will the annoying error 135 window pop out or not?

- Clearpicks

[NinjaTrader_Ray]

Don't know what causes this. Works as expected here in the test cases you provided and we have never had any other reports so I am at a loss at this time.

[clearpicks]

Does NinjaTrader use IB's propietary API to communicate with IB TWS? I am using IB TWS 884.6, Java 1.6.0_05.

- Clearpicks

[NinjaTrader_Dierk]

Not sure what you mean nor why that would matter.

[clearpicks]

It does not matter. The IB's proprietary API is just the IB socket based API, which IB calls it its proprietaty API. In contrast, non-proprietary API is the FIX.

I just provided a little more information so as to help you guys to find out why, thus to fix the issue as soon as possible. Thanks.

- Clearpicks

[clearpicks]

What does the "Run-time pop up handing" in Connection Options windows mean? Does it have anything to do with the error 135 message window?

- Clearpicks

[NinjaTrader_Dierk]

Not that I'm aware of. You could try checking/unchecking it.

[clearpicks]

It seems making no difference regarding to the error 135 message. Then what is it for?

- Clearpicks

[NinjaTrader_Dierk]

http://www.ninjatrader.com/webnew/support_interactivebrokers.htm

Run-time pop up handling – Enables NinjaTrader to suppress TWS pop up windows