I got this running a couple months ago with out a hitch, but dont remember much of the details..
ther.jar:rss.jar -Xmx1024M jclient.LoginFrame .
ther.jar:rss.jar -Xmx512M jclient.LoginFrame .If you are using IBController to start up TWS then on 64 bit CPU's you definitely need MaxPermSize=128M or you will get the out of memory error you describe. At least that has been my experience. I'm not sure that using -XX:+AggressiveHeap is a good idea. It overrides your -Xmx512M parameter and actually makes it easier to run out of memory in some cases. Here is snippet from the Sun documentation:Quote from number22:
Testing my first 64bit Linux installation, Oracle/Sun java 64 bit 1.6.0.u25 as well.
using IB original starting scripts:
java -cp jts.jar:hsqldb.jar:jcommon-1.0.12.jar:jfreechart-1.0.9.jar:jhall.jarther.jar:rss.jar -Xmx512M jclient.LoginFrame .
after hours running, IB TWS starting freezing up with OutOfMemoryError problem. this happened only with java 64 bit version, i haven't seen this on 32 bit before, and I think it isn't hardware problem. Anyway, I add both -XX:MaxPermSize=128M and -XX:+AggressiveHeap into starting script, hoping it will help remedy this outofmemory problem.
Because this option sets heap size, do not use the -Xms or -Xmx options in conjunction with -XX:+AggressiveHeap. Doing so will cause the options to override each other's settings for heap size.
This option should be used with caution. Because it makes the JVM greedy with memory resources, it is not appropriate for many programs and makes it easier to run out of memory. For example, by using most of the 4GB address space for heap, some programs will run out of space for stack memory. In such cases -Xss may sometimes help by reducing stack requirements.
Quote from mikesmithv:
If you are using IBController to start up TWS then on 64 bit CPU's you definitely need MaxPermSize=128M or you will get the out of memory error you describe. At least that has been my experience. I'm not sure that using -XX:+AggressiveHeap is a good idea. It overrides your -Xmx512M parameter and actually makes it easier to run out of memory in some cases. Here is snippet from the Sun documentation: