The application is platform independent (written in java) But there is something between the platform and the application - the java virtual machine (jvm). And it converts java to machine code etc in a very platform dependent way. So on w7x64 you install both the 32 bit and 64 bit versions of the java virtual machine to give your app software maximum compatibility options.
The following simple procedure allowed me to run TWS with 64-bit Java, without installing 32-bit Java at all. I'm running Windows 7 Pro 64-bit. Initially i had no Java and no TWS installed. First, I installed 64-bit Java (version 7 update 6), and then i installed TWS Standalone build 929 for Windows. I did not install 32-bit Java at all. When I double-clicked the TWS shortcut on the desktop, Windows started searching for javaw.exe while giving me the option to "Browse" to the file manually. I clicked on the little Browse button and selected: C:\Program Files\Java\jre7\bin\javaw.exe Then I double-clicked the TWS desktop shortcut again, and now am logged in and running TWS on 64-bit windows with 64-bit Java, and without having to install 32-bit Java.
forgive a small blast to the past, but I haven't been by in a while and looking at You realize what you've done is copy 32 bit Java into the 64 bit system folder (System32). Anything looking for 64 bit java will look there and end up with 32 bit java. Any java, be it 32 bit or 64 bit, should be installed to their appropriate folder. You edit the command line in the shortcut to specify which version you wish to run, be it SysWOW64 for the 32 bit version, or System32 for the 64 bit version. I'm running against system32 for 1.7.21, giving it 3gb to run with. Running fine, except for some issues getting book data through the API, which I'm suspecting is an issue with the 3rd party software, not TWS, nor its API nor Java.
somewhat interesting that this bug/thread which started in 2007 still persists in 2013. I had same issue as OP: Didn't seem to matter whether I used 64bit or 32bit java, same error. Instead I found a random jts.ini file on google and copied it jts directory, fixed it right away. Didn't see this elsewhere, here is the file Code: [Logon] Locale=en Steps=23 useRemoteSettings=true os_titlebar=false colorPalletName=classic UseSSL=false [settings] zzobgpwt=1293124449552 [communication] Peer=gw4.ibllc.com:4000 Region=us
I've read this entire thread and here's my computer issue, similar to Canoe007. Like clockwork at noon and after 4pm my TWS freezes. I can tell its about to freeze as everything gets sluggish, then boom. I get the AppHangB1 with javaw.exe and I can close the frozen TWS and relog in fine. I have a Win7 machine with 8GB and 64-bit. I have installed java 32-bit and 64-bit(don't remember the order) and standalone TWS. I have this bumped up from default: -Xmx1536M -XX:MaxPermSize=256M and it is running from C:\Windows\System32\javaw.exe any suggestions? Oddly enough I am also running another TWS on my laptop and it hasn't frozen recently(though both did the same thing in the first few days I used them). Windows Vista, 3GB, 32bit. -Xmx1024M -XX:MaxPermSize=128M C:\Windows\System32\javaw.exe with only Java 7.0.25 32-bit kind maybe take off 64-bit on the windows 7 machine? reinstall both java's? change xmx/permsize? help...
This is the error I'm getting: Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: javaw.exe Application Version: 7.0.250.17 Application Timestamp: 51c4b1ff Hang Signature: 79ae Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Hang Signature 1: 79ae138297242cd44a728c366703050b Additional Hang Signature 2: f658 Additional Hang Signature 3: f65810502fddfb3cb0b566ab62f7b490 Additional Hang Signature 4: 79ae Additional Hang Signature 5: 79ae138297242cd44a728c366703050b Additional Hang Signature 6: f658 Additional Hang Signature 7: f65810502fddfb3cb0b566ab62f7b490
I updated my TWS. Tried to open TWS. Received error message: could not create the java virtual machine Solution: http://www.tomshardware.com/faq/id-1761312/fix-create-java-virtual-machine-issue.html Open the Control Panel {Go to System and Security} Go to System Go to Advanced Systems Properties {In Windows 7 this is Advanced Systems Settings} Then Environment Variables In System Variables, click Add New Variable Name: _JAVA_OPTIONS New Variable Value: -Xmx512M Click OK See http://www.jafaloo.com/2011/10/30/java-xmx-memory-settings/ for more details on Java Heap memory size and parameters.