We have been customers with IB for four and a half years and there was a time before when they had data problems. They changed the basic datafeed structure so it would "never happen again". LOL here we are again. It is all this darn tinkering they do with their stuff - their basic philosophy is wrong. Why cannot they be just a darn good broker? No they have to fart around with charts and bells and whistles etc etc. Am wondering when they will finally wake up to the fact that Java is the proverbial POS. It won't even take advantage of a duo core CPU. Having said all this, it should not have suprised anyone. What does one expect when a computer geek is in charge? Maria
Am sorry but you are mistaken. Java is only utilising one CPU and is not multi threading. This leads to inconsistent behaviour like when starting IB's TWS up you have at times first to minimize TWS and then restore again before you can see the quotes. This never happened in the 4 years we were using single core CPU's. If starting up two TWS accounts then they get both allocated to the same CPU / core creating an imbalance in the load. Sorry that I have not better news for you. Maria, over and out with this discussion.
Java most certainly supports multi-threading. If you don't believe me read the Java Doc starting, I suggest, with the Thread class. What's more, Java threads are mapped directly onto operating system (native or kernel ) threads ie one Java thread => one operating system thread. The operating system (Windows or Linux) will schedule threads across available CPUs. All this is fact. I have on the screens in front me real time charts generated by Java software I have written and I assure you it is multi threaded. http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Thread.html
lol a IB data feed problems now becomes Java multi-thread problem... anyway, Java is multi-thread & multi-cpu but Swing is single-thread.