Invalid initial heap size Problem with sdk1.4.2_03

Question

Hi,
ich habe a troubling error with the java version 1.4.2_03.
I use an Ant Task to start a Weblogic Server (J2EE Server). For this, I use the following Ant code :
-----ANT CODE------------------------------------------------------------------------------------------------------------------------
<java classname="weblogic.Server" fork="true" failonerror="true" dir="${weblogic.domain.dir}">
<sysproperty key="bea.home" value="${bea.home.dir}"/>
<sysproperty key="weblogic.Name" value="${weblogic.admin.server.name}"/>
<sysproperty key="weblogic.management.username" value="${weblogic.user.name}"/>
<sysproperty key="weblogic.management.password" value="${weblogic.user.password}"/>
<sysproperty key="weblogic.ProductionModeEnabled" value="false"/>
<sysproperty key="java.security.policy" value="${weblogic.home.dir}\server\lib\weblogic.policy"/>
<sysproperty key="weblogic.security.SSL.trustedCAKeyStore" value="${weblogic.home.dir}\server\lib\cacerts"/>
     <jvmarg value="-Xms32m -Xmx200m"/>
<classpath>
<pathelement path="${windows.classpath.wls}"/>
</classpath>
</java>
-----/ANT CODE------------------------------------------------------------------------------------------------------------------------
This Task perfectly works with the sdk java version 1.4.1_05, but I have the following message with the sdk java version 1.4.2_03 :
-----ERROR MESSAGE---------------------------------------------------
Invalid initial heap size: -Xms32m -Xmx200m
Could not create the Java virtual machine.
-----/ERROR MESSAGE---------------------------------------------------
The following parameter is anymore correct : <jvmarg value="-Xms32m -Xmx200m"/>
I have tried with a lot of possibilty, 64-200, 128-200, 128-128, 256-256, 512-512, nothing works.
I have tried without this parameter, this works fine.
I have tried with the weblogic server without the Ant Task, and this works fine too.
I think this is a bug in the JVM 1.4.2_03.
What do you think about this problem ??? Do you have some solution ???
I have also tried with another version of ant, I have the same problem. This works with JVM 1.4.1_05 and not with JVM 1.4.2_03.
If you have an idea, please, help.
Thanks

Answer 1

If you can start a 1.4.2 JVM with all these parameters independently (i.e. not from Ant) and it works, but from Ant it doesn't work, it's more likely that the problem is somehow related to interaction between Ant and the JVM, rather than the JVM itself. So I would suggest trying some Ant forum first - I think it would also work faster than if you try to submit this bug to Sun.