IB reps,
I really didn't expect you to stick to the auto logoff so hard, but uhmm..., ok.
BUT PLEASE FIX THIS BUG:
When the TWS is connected to an (Socket-) API client,
it crashes on exit (not in every case).
When you close TWS main window (no matter if via Menu, ALT-F4 or even Auto-Logoff), javaw.exe goes dead and you get a non-responsive application.
You need to kill it via task manager.
This bug was fixed in earlier versions, but is back in 851.
I cannot reasonably automate the administration of my hardware systems if I have to care about a maybe-zombie javaw.exe process in background.
My config is standard: XPSP2, Sun Java 1.5 (04), build 851 and connection via LAN routers. Nothing unusual.
Please do something here !!!
I really didn't expect you to stick to the auto logoff so hard, but uhmm..., ok.
BUT PLEASE FIX THIS BUG:
When the TWS is connected to an (Socket-) API client,
it crashes on exit (not in every case).
When you close TWS main window (no matter if via Menu, ALT-F4 or even Auto-Logoff), javaw.exe goes dead and you get a non-responsive application.
You need to kill it via task manager.
This bug was fixed in earlier versions, but is back in 851.
I cannot reasonably automate the administration of my hardware systems if I have to care about a maybe-zombie javaw.exe process in background.
My config is standard: XPSP2, Sun Java 1.5 (04), build 851 and connection via LAN routers. Nothing unusual.
Please do something here !!!