|
|
Before using the Oracle JRockit JDK, you need to make sure that it is set up correctly. This section gives you hints on how to set up your environment for your specific platform. Once you have configured the environment correctly, you will find the diagnosing process easier. The configuration is done in the following steps:
The JRockit JDK is included in several Oracle products, for example Oracle JRockit Mission Control, Oracle JRockit Real Time and Oracle WebLogic.
The Linux operating systems exist in a large number of updates and patches. Oracle personnel is not able to test the JRockit JDK against every patch that is released. Instead we intend to test the most recent releases of some few distributions. As a general rule, you should keep your Linux environment up to date and make sure you have a release that is supported by Oracle when running the JRockit JDK. Please see the Oracle JRockit JDK Supported Configurations document for a list of releases and distributions that the JRockit JDK has been successfully tested against.
The following path is the correct path for Linux installations:
export PATH=$HOME/jrockit-<jrockit_version>-jdk<sun_version>/bin:$PATH When running the Oracle JRockit JVM on Linux IA32, it must be configured to use the glibc compiled for i686 architecture, otherwise you will see freezes and crashes with the JRockit JVM.
Check which glibc is installed by running:
rpm -q --queryformat ‘\n%{NAME} %{VERSION} %{RELEASE} %{ARCH}\n’ glibc
When using the JRockit JDK 1.4.2 on Linux, you should first make sure that the environment variable LD_ASSUME_KERNEL is not defined. If LD_ASSUME_KERNEL is defined, the JRockit JVM will use an older and slower threading implementation, which can deter—and will not improve— performance.
In some Linux versions the /proc filesystem isn’t mounted when running in a chroot(3) environment. This may cause the JRockit JVM to become unstable or crash when running in the chroot(3) environment, as the JVM and some Linux libraries need to access information about the hardware platform from /proc.
To verify that /proc is mounted you can issue the shell command getconf _NPROCESSORS_CONF from the command line in your chroot(3) environment. This command should return the correct number of processors on your system, otherwise you will have to mount the /proc filesystem before running the JRockit JVM.
There are a number of environment variables that control the operation of the JRockit JVM on Windows. The following PATH environment variable needs to point to the directory of your Java installation:
set PATH=%ProgramFiles%\Java\jrockit-<jrockit_version>-jdk<sun_version>\bin;%PATH%
The following path is the correct path for Solaris installations:
export PATH=$HOME/jrockit-<jrockit_version>-jdk<sun_version>/bin:$PATH Oracle JRockit JDK is included in several products, for example Oracle JRockit Mission Control, Oracle JRockit Real Time and Oracle WebLogic. For more information, see the installation guides for your specific Oracle product.
| Note: | Technical license checks have been removed as of this rel;ease. The following instructions apply only to versions of JRockit JDK prior to R27.6. |
You can set the path to the license file by using the -Djrockit.license.path flag at startup. This option is useful when:
The option should point to a directory where the license.bea file resides and not directly to the license.bea file; for example:
|