I believe the latest versions of TWS require Java in the 1.4 series. You can't really use the Microsoft VM for XP era OS installs (unless something changed regarding the settlement again). (The MS VM has not been updated and MS doesn't support Java.) MS IE users who have XP SHOULD use the Sun plug-in. (Microsoft Knowledge Base article #163637)
I just deleted out all previous Java and TWS remnants (used RegCleaner as well) reinstalled both Java and TWS and it seems fine. BUT the final test will be to-morrow when the quotes are coming a million a minute.
More info Microsoft knowledge base article #813926 (I've got a pristine XP install and I don't have the MS VM according to this test.) To determine if you are running the Microsoft VM, follow these steps: Click Start, and then click Run. Type cmd, and then click OK. At the command prompt, type jview and then press ENTER. If you are not running the Microsoft VM, you receive the following error message: "'jview is not recognized as an internal or external command, operable program or batch file. " From knowedge base article #163637 The Microsoft VM is not included with Windows Server 2003, the original version of Windows XP, or Windows XP SP1a. From knowledge base article #214828. JDK compatibility with MS Java VM. Internet Explorer 5.5 - MS VM build 3309 (or greater) - JDK 1.1.4, includes JNI (That's the latest and greatest. Nothing more after that.) The current version (or build number) of the Microsoft virtual machine (Microsoft VM) is 3810. (This tells you that the latest MS VM corresponds to an old version of Java which may not run TWS well.) Microsoft does not provide a downloadable version of the Microsoft VM for computers that do not already have the Microsoft VM installed. If you do not have the Microsoft VM installed, you cannot install updates to the Microsoft VM. Windows Update does not offer updates to the Microsoft VM if the Microsoft VM is not installed on your computer.
In my experience as a server-side architect, Webogic is definitely the leader in this category...and blows away any other server in any other language, in both speed and stability. the problem is with the AWT/SWING packages that Java currently uses to render graphics and trigger OS operations -- not as powerful as their counterparts. For high-powered applications, Java is still gonna be slower than native apps on Windows, b/c the virtual machine (VM) needs to run on top of the Windows OS. Much slower? Not really. Unstable, nope. No memory leaks, no inadvertantly dumping or addressing incorrect memory addresses. Sadly, Microsoft has refused to open up certain parts of their OS to the architects of the Java language so they can code a better VM. Microsoft's goal is to provide special hooks into the OS via the Microsoft VM and then slowly force everyone to use its special features to make the Java apps run quicker. (They are, of course, trying to compete with their own .NET architecture, which in my experience is hugely flawed) The idea of Java trashing your OS sounds like you need to learn some things about your computer and how its software works. Java runs a virtual machine that sits on top of your computer, and is COMPLETELY independant. You can even run multiple virtual machines at the same time with the same app or different apps if you choose. The virtual machine does little to effect the setup of your computer ... it doesn't fuck with the registry like other applications or try to share .dll files that might be registered to other applications. It keeps the application very isolated (that was the goal) from the OS layer. LongShot is correct, Java, like Linux, will eventually overtake everything else (even with all of Gates' power and money) simply because of the open source community. When this happens is the only question. Java seems likely to reach this goal first.
Do not use the MS Java 1.1 thing (aka MS Java VM). It´s an outdated technology not even supported by MS. The only thing it does is to compromise your system security. Current Java Version is 1.4.x.x made by Sun www.JavaSoft.com
I am using multiple java applications simultaneously even with different versions of the sun jre and have absolutely no problems.
Sun Java 1.4.1_02 was a mild disaster on my Windows XP system. TWS ran fine, but other sites' Java applets would occasionally cause IE to die or wedge. 1.4.1_01 is fine. I've swapped back and forth between the two a few times and confirmed this - I really wanted to give the _02 version a try, because Sun bundles it in with their Sun ONE Studio developer platform, which I want to use. I'll try 1.4.1_03 this weekend and see how it goes. 1.4.1 also made thinkorswim's trading client (which, when I tried it a couple months ago, was written for 1.3) wedge occasionally - I wonder if thinkorswim supports 1.4 now.
When you use TWS standalone version then there is no need to enable "Sun Java PlugIn" for your MS IE. You can turn it off and let "MS JVM PlugIn" run all the other java applets that you may encounter surfing the web with your MS IE.
has anyone managed to get tws working with an externally hosted java server - say on another machine on the lan?