Forum Discussion

BA_Service_Haus's avatar
BA_Service_Haus
Regular Contributor
12 years ago

[Res] soapUI Pro 4.6.0 32-bit: cannot run testrunner.bat

Hi everyone,

when calling testrunner.bat in soapUI Pro 4.6.0 32-bit the following error is returned:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.


I already tried to vary xmx and xms values in soapUI-Pro-4.6.0.vmoptions but that didn't help.

With soapUI Pro 4.6.0 64-bit this error doesn't occure.

Best regards
Nico
  • nmrao's avatar
    nmrao
    Icon for Champion Level 2 rankChampion Level 2
    12 years ago
    Just a quick check, are you using 32-bit java and still failing in your case?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    We couldn't reproduce your problem when testing, so it may be because you're using 64-bit Java with 32-bit SoapUI.

    Regards,
    Manne
  • BA_Service_Haus's avatar
    BA_Service_Haus
    Regular Contributor
    12 years ago
    Hi,

    first of all:
    - I'm using the bundle installer, so I expect to use the correct jre-version.

    Nevertheless I now could solve the problem.
    It was caused by the xmx-value, which had to be decrease.

    I thought, I already did this by changing the values in "soapUI-Pro-4.6.0.vmoptions", but these values are not used in testrunner.bat.
    Instead I had to change the xmx-value hardcoded in testrunner.bat from 1024m to 998m.

    Not everything works fine.
    (I still wonder why this behaviour is different to our last soapUI Pro version 4.0.1.)

    Best regards
    Nico
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Good thing you solved it!

    I can't check at the moment, but it's possible that the Xmx value has been increased in later versions of SoapUI, which seems reasonable but could of course cause problems when memory is scarce.

    Kind regards,

    Manne
  • BA_Service_Haus's avatar
    BA_Service_Haus
    Regular Contributor
    12 years ago
    Hi Manne,

    the xmx value is equal to the one, that we use with soapUI Pro 4.0.1.
    But of course the jre, included in the bundle, changed in the meantime.

    Best regards
    Nico
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Depending on JVM and operating system version the maximum Xmx value that can be used on a 32-bit JVM varies a bit. In my experience the maximum value usually varies between 1200m and 1500m.

    If you are having a 64-bit operating system I recommend using the 64-bit version of SoapUI. Using the 64-bit version this problem of maximum amount of memory wont appear.

    Regards,
    Joel Jonsson
    SmartBear Sweden
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    12 years ago
    Hi, i've also noticed this problem in the past just after applying a patch on windows 32 bits (server 2003).
    Because of this patch, I could not start a jvm with more than 999m!! (fixed with http://support.microsoft.com/kb/971812)
    Don't know if this is the same root cause as for "BA Service Haus Support"
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Thank you for pointing that out, redfish4ktc2. That might very well be the root cause for some people experiencing this.

    Regards,
    Arian
    SmartBear Sweden