a bug in IB Plugin 1083

[clearpicks]

I am using IB Plugin 1083 and esignal 1086. There is no problem to execute orders via IB plugin. If IB TWS is closed and reopened, IB plugin can automatically get reconnected (because it always retrying to get connected in build 1083). But if at this time, there are existing positions in IB TWS (taken before IB TWS was closed), sometimes closePosition() donot work any more (both no response and message in IB TWS and in integrated trading window). In some cases it may resume to work after adding more contracts to the existing positions, while in other cases shutdown and restart is the only solution.


- Clearpicks

[clearpicks]

Re: a bug in IB Plugin 1083

It seems the cancelOrder(symbol) does not work either after IB TWS is shutdown and restarted and IB plugin gets automatically reconnected. Even if IB plugin is manually disconnected and connected again, the two API functions still would not work anymore. Only way to solve the problem is to restart esignal.
Please acknowledge that this problem has been added to the bug tracking list. Thanks.

Originally posted by clearpicks
I am using IB Plugin 1083 and esignal 1086. There is no problem to execute orders via IB plugin. If IB TWS is closed and reopened, IB plugin can automatically get reconnected (because it always retrying to get connected in build 1083). But if at this time, there are existing positions in IB TWS (taken before IB TWS was closed), sometimes closePosition() donot work any more (both no response and message in IB TWS and in integrated trading window). In some cases it may resume to work after adding more contracts to the existing positions, while in other cases shutdown and restart is the only solution.


- Clearpicks