Well looking at your startup sequence, there definitely is conflicting info there, check your command line at the highlighted sections (sorry, this is just set bold, so if your mail agent does not do RTF, bad luck) ...
VM start exception: VM initialization failed for: C:\Program > Files\Java\jdk1.6.0_12\jre\bin\java *-Xms256m -Xmx512m*-Dofbiz.home=E:/ofbiz > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\Program Files\Apache Software > Foundation\Tomcat 6.0\conf\loggi > ng.properties *-Xms512M -Xmx1024M* -XX:MaxPermSize=512M > -Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation\Tomcat > 6.0\endorsed -classpath C:\Program > Files\Java\jdk1.6.0_12\lib\tools.jar;C:\Program Files\Apache Software > Foundation\Tomcat 6.0\bin\bootstrap.jar -Dcatalina.base=C:\Program Fi > les\Apache Software Foundation\Tomcat 6.0 -Dcatalina.home=C:\Program > Files\Apache Software Foundation\Tomcat 6.0 -Djava.io.tmpdir=C:\Program > Files\Apache Software Foundation\Tomcat 6.0\temp -Xdebug > -Xrunjdwp:transport=dt_shmem,address=javadebug72599,suspend=y > org.apache.catalina.startup.Bootstrap start > so your "exploded" startup line (amended by the Tomcat scripts) specifies two different initial and two different max Heap Sizes. I recommend two things: * set -Xms512M to both and -Xmx1024M to both values * if this is your production configuration, make sure you min and max setting are identical in order to reach good performance. Regards Carsten
