Integration

Not enough storage is available to process this command in tsStartJavaThread. The 'd' got chopped off the subject because of the field-length limitations.

Running Eclipse on Jrockit with a lot of plugins results in the following error:

Not enough storage is available to process this command in tsStartJavaThread (src/jvm/threads/vmthread/lifecycle.c:1096).
Java heap 750M reserved, 750M committed
Paged memory=146456K/2147352575.
Your Java heap size might be set too high.
Try to reduce the


Because the SUN-Oracle JVM is much less stable, and crashes randomly with my Eclipse configuration, therefore I'm using using JRockit. I've used the R28.1.0 JVM in jrockit-jdk1.6.0_20-R28.1.0-4.0.1-windows-ia32 ( http://download.oracle.com/otn/bea/jrockit/jrockit-jdk1.6.0_20-R28.1.0-4.0.1-windows-ia32.exe ) and JRockit JVM R27.6.5 Jrmc-4.0.1-1.6.0 , in combination with the following heap-space sizes: 1350, 1150, 950, 800 & this time 750 MB, but the issue still persists. I get the error message the quickest when I use CodePro AnalytiX to generate JUnit Testcases ( http://code.google.com/javadevtools/codepro/doc/index.html ) or repeatedly use SDE ( http://www.visual-paradigm.com/product/sde/ ). After that the Eclipse workbench becomes unstable and mostly unresponsive and constantly request permission to exist the workbench (and sometimes the JVM even downright crashes), which doesn't help much other than starting the above scenario all over again. I'm not interested in testing in other Eclipse configurations. I'm using MyEclipse for Spring v8.6 32bit ( http://www.myeclipseide.com/spring.php ) which is based on Eclipse 3.5 (Galileo).

Anyone knows what's really going on? And how to go about this? Or should I post this somewhere else?

Edited by: b4l4nc3r on Jan 2, 2011 2:45 PM