You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
IB disconnections
- Thread starter 0008
- Start date
Quote from vikana:
I suggest you switch to the JVM that IB supports. They are pretty clear on their web site that they support JVM 1.5 (they don't list JVM 1.6)
I'm on JVM 1.5 and generally TWS works fine. Everyone i know who've tried 1.6 end up switching back to 1.5 for a variety of reasons (connectivity, UI being messed up etc.)
Interestingly the one supported may not be the best one. I know of a lot of people here who moved to the late 1.6's and are still happily using them. Most of the 1.6 problems were in the early stages of 1.6 (_3 or before) with earlier TWS's. One of the Sierra Chart users recently had problems that could be related to the ones described here and when they moved from 1.5._latest to 1.6.0_7 the problems disappeared.
Quite a few people on ET have been using 1.6.0_10 since beta 25 to overcome a problem they saw with _6 or _7 and its been very good. It's a major performance and reliability revision for Java, due for release late summer and currently its been at release candidate for quite a few weeks (b28 is the rc). I'd recommend it to any TWS user with current versions of TWS (885 plus, say).
https://jdk6.dev.java.net/6u10ea.html
I fully agree as I was wondering that myself so I hunted down the problem:Quote from Tums:
If Java is the problem, then thousands of people who use the same Java will get disconnect problem the way you do.
In the System Properties - Performance - Advanced of Windows XP "Memory Usage" was set to give "System Cache" a greater share of memory to run.
My TWS disconnect problems all disappeared after I changed "Memory Usage" to "Programs."
Maybe this will help someone.
Everyone have a great weekend!