Oracle JDeveloper 11.1.1.3.0 – configuration of the integrated WebLogic Server instance to run using Oracle JRockit JVM

This post presents the settings needed  in order to change the JVM used by the integrated WebLogic Server instance from Oracle JDeveloper 3.0 to Oracle JRockit JVM.Many times when an ADF application is running several times in the JDeveloper an out of memory exception appears. This is because the standard JVM, which comes with the JDeveloper kit, is mainly optimized for development and not for continuous running of real applications. So, also the integrated WebLogic instance will run using the same JVM. In order to overcome this problem, the JVM used by the integrated WebLogic Server instance can be changed to Oracle JRockit JVM that is well known as the JVM chosen in “production”. Below are the steps needed for this configuration:

Step 1: Download and install Oracle JRockit JVM from the Oracle official site.

Step 2: Open the file <appdata path>\system<version>\DefaultDomain\bin\setDomainEnv.cmd.

Step 3: Change the following lines from the filesetDomainEnv.cmd:
set BEA_JAVA_HOME=<path to JRockit home directory>
set JAVA_VENDOR=Oracle.

Step 4: Restart the integrated WebLogic Server from JDeveloper and the log should display something like that:
...
Starting WLS with line:
C:\Oracle\JRRT-4~1.0-3\bin\java -jrockit ...
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Oracle JRockit(R) (build R28.0.1-21-133393-1.6.0_20-20100512-2132-windows-ia32, compiled mode)....

Note that, only the WebLogic Server will use the Oracle JRockit JVM and that JDeveloper is using its own JVM. It is possible, also, to change that by replacing the JDK home directory setting SetJavaHome from the configuration file <path to jdeveloper>\jdev\bin\jdev.conf with Oracle JRockit home directory.