What problems are you having with latest TWS?

[syswizard]

Quote from kostia00:
We have found that a certain piece of load-balancing hardware that distributes the incoming TWS connections over a pool of servers was misconfigured, and was dropping connections when TWS would get busier and less responsive.
The hardware has been reconfigured as of Monday Apr 30th, and we see the number of disconnects went down significantly. There are still some disconnects attributable to two copies of TWS running on two computers for the same user name, and some disconnects would always be attributable to ISP problems. If you believe you are getting disconnects not caused by either ISP or second copy of TWS, please PM me your user name and we at IB will investigate.

This is good work, but two things:
1) what steps has IB technical management taken to insure this won't happen (or a similar hardware issue) in the future ?
2) I was told two (or more) copies of TWS can exist on the same machine (or network) as long as the port numbers were different. Has support for this configuration changed or has this dual set-up been shown to have reliability problems ?

 

[dcraig]

Quote from syswizard:

This is good work, but two things:
2) I was told two (or more) copies of TWS can exist on the same machine (or network) as long as the port numbers were different. Has support for this configuration changed or has this dual set-up been shown to have reliability problems ?

But only if logged into different accounts, I believe. Only one login per account.

 

[risktaker]

Everything running smoothly for me last couple of days. No pinkouts and basket trader issues appear resolved. Wow!

Happy camper today.

 

[kostia00]

Quote from syswizard:

2) I was told two (or more) copies of TWS can exist on the same machine (or network) as long as the port numbers were different. Has support for this configuration changed or has this dual set-up been shown to have reliability problems ?

This setup works as long as those two or more copies of TWS log into different sessions (use different usernames). Each username can only be used by one TWS or one WebTrader session at any given time.

I am not in the position to answer your other question, but I will relay it to the appropriate managers.

 

[Bob111]

Quote from risktaker:

Everything running smoothly for me last couple of days. No pinkouts and basket trader issues appear resolved. Wow!

Happy camper today.

no disconnections/login problems here.
the only new thing i notice today,when i tried to place order is new pop up saying-
"order would cross related resting order"
have no idea what it's mean and never seen this one before.
can anyone from IB explain,what it mean?

Thank you!

 

[samaritan]

Quote from Bob111:

no disconnections/login problems here.
the only new thing i notice today,when i tried to place order is new pop up saying-
"order would cross related resting order"
have no idea what it's mean and never seen this one before.
can anyone from IB explain,what it mean?

Thank you!

This was due to a problem with new compliance code we are rolling out. It was deactivated.

 

[syswizard]

Quote from samaritan:

This was due to a problem with new compliance code we are rolling out. It was deactivated.

Believe it or not, the above is a little bit SCARY. Are you guys trialing/beta-testing this stuff BEFORE rollout ? I mean, do you have a hard-core group of users/advocates who will spend the time trying your new releases before the masses get them ?

 

[syswizard]

Quote from kostia00:

This setup works as long as those two or more copies of TWS log into different sessions (use different usernames). Each username can only be used by one TWS or one WebTrader session at any given time.

This doesn't jive with what the API forum has been telling me. They've been saying if I want separate instances, say of Excel, one running a certain set of stocks, and another instance of Excel running futures, that each instance should be logging on with the same account, but different PORTS, and one with a clientID of say "77", the other with "0". The "0" instance can see all trades posted by "77" and itself.
CAN WE PLEASE GET THIS STRAIGHT ?

 

[kostia00]

Quote from syswizard:

This doesn't jive with what the API forum has been telling me. They've been saying if I want separate instances, say of Excel, one running a certain set of stocks, and another instance of Excel running futures, that each instance should be logging on with the same account, but different PORTS, and one with a clientID of say "77", the other with "0". The "0" instance can see all trades posted by "77" and itself.
CAN WE PLEASE GET THIS STRAIGHT ?

My comment was about multiple TWS copies for a single user. Each TWS instance running on a machine can accept many API clients (Excel or others), as long those API clients use distinct clientIDs. Hope this clarifies it, thanks.

 

[Catoosa]

Trouble with TWS version 871.3. Today, I upgraded TWS from 870.2 to 871.3 and found my single chart disconnected from the server after TWS had been opened for about 5 to 6 minutes. I could refresh the chart and after 5 to 6 minutes the chart would again disconnect. I downgraded TWS back to version 870.2 and have had no chart disconnections.

Catoosa