PM52774: A large maximum heap size cannot be used after upgrading to v126.96.36.199
Closed as program error.
Abstract: After upgrading to Rational Application Developer v188.8.131.52 the eclipse.ini references the IBM JVM by loading the jvm.dll in-process. Any attempts to increase the maximum heap size to 1792m will result in a message 'Failed to create the Java Virtual Machine'. Problem: This problem only occurs on a 32-bit Windows platform with the /3GB switch enabled as described here: http://msdn.microsoft.com/en-us/windows/hardware/gg487508 Before upgrading the product to v184.108.40.206 the eclipse.ini file contained the following: -vm ?product install?\jdk\jre\bin\javaw.exe and you could set the maximum heap size by modifying the following line in this file: -Xmx1024m to -Xmx1792m and the product would launch under these conditions. However, after upgrading to Rational Application Developer to v220.127.116.11 the eclipse.ini contains: -vm C:\Program Files\IBM\SDP\jdk\jre\bin\j9vm\jvm.dll and any attempts to start the product with a large maximum heap size produces the error: 'Failed to create the Java Virtual Machine'. Local fix: Open the eclipse.ini file located in the product installation directory and change the line: -vm ?install directory?\jdk\jre\bin\j9vm\jvm.dll to: -vm ?install directory?\jdk\jre\bin\javaw.exe
The product will fail to launch when a large heap size is used as a result of launching the JVM using jvm.dll rather than javaw.exe.
The product will now launch using the javaw executable. The fix for this APAR is included in Rational Application Developer v18.104.22.168 iFix1.
Reported component name
RATL APP DEV WI
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL APP DEV WI
Fixed component ID
Applicable component levels
Translate this page: