Installing and using OpenJDK 8 for RHEL
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Providing feedback on Red Hat documentation
We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments.
This section explains how to submit feedback.
Prerequisites
- You are logged in to the Red Hat Customer Portal.
- In the Red Hat Customer Portal, view the document in Multi-page HTML format.
Procedure
To provide your feedback, perform the following steps:
Click the Feedback button in the top-right corner of the document to see existing feedback.
NoteThe feedback feature is enabled only in the Multi-page HTML format.
- Highlight the section of the document where you want to provide feedback.
Click the Add Feedback pop-up that appears near the highlighted text.
A text box appears in the feedback section on the right side of the page.
Enter your feedback in the text box and click Submit.
A documentation issue is created.
- To view the issue, click the issue tracker link in the feedback view.
Chapter 1. OpenJDK 8 overview
OpenJDK (Open Java Development Kit) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in three versions: OpenJDK 8u, OpenJDK 11u, and OpenJDK 17u.
Packages for the Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Ecosystem Catalog.
Chapter 2. Installing OpenJDK 8 on Red Hat Enterprise Linux
OpenJDK is an environment for developing and running a wide range of platform-agnostic applications, from mobile applications to desktop and web applications and enterprise systems. Red Hat provides an open source implementation of the Java Platform SE (Standard Edition) called OpenJDK.
Applications are developed using the JDK (Java Development Kit). Applications are run on a JVM (Java Virtual Machine), which is included in the JRE (Java Runtime Environment) and the JDK. There is also a headless version of Java which has the smallest footprint and does not include the libraries needed for a user interface. The headless version is packaged in the headless subpackage.
If you are unsure whether you need the JRE or the JDK, it is recommended that you install the JDK.
The following sections provide instructions for installing OpenJDK on Red Hat Enterprise Linux.
You can install multiple major versions of OpenJDK on your local system. If you need to switch from one major version to another major version, issue the following command in your command-line interface (CLI) and then following the onscreen prompts:
$ sudo update-alternatives --config 'java'
2.1. Installing a JRE on RHEL by using yum
You can install OpenJDK Java Runtime Environment (JRE) using the system package manager, yum
.
Prerequisites
- Logged in as a user with root privileges on the system.
- Registered your local system to your Red Hat Subscription Management account. See the Registering a system using Red Hat Subscription Management user guide.
Procedure
Run the
yum
command, specifying the package you want to install:$ sudo yum install java-1.8.0-openjdk
Check that the installation works:
$ java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)
NoteIf the output from the previous command shows that you have a different major version of OpenJDK checked out on your system, you can enter the following command in your CLI to switch your system to use OpenJDK 8:
$ sudo update-alternatives --config 'java'
2.2. Installing a JRE on RHEL by using an archive
You can install OpenJDK Java Runtime Environment (JRE) by using an archive. This is useful if the Java administrator does not have root privileges.
To ease the upgrades for later versions create a parent directory to contain your JREs and create a symbolic link to the latest JRE using a generic path.
Procedure
Create a directory to where you want to download the archive file, and then navigate to that directory on your command-line interface (CLI). For example:
$ mkdir ~/jres $ cd ~/jres
- Navigate to the Software Downloads page on the Red Hat Customer Portal.
- Select the latest version of OpenJDK 8 from the Version drop-down list, and then download the JRE archive for Linux to your local system.
Extract the contents of the archive to a directory of your choice:
$ tar -xf java-1.8.0-openjdk-portable-1.8.0.322.b06-4.portable.jre.el7.x86_64.tar.xz -C ~/jres
Create a generic path by using symbolic links to your JRE for easier upgrades:
$ ln -s ~/jres/java-1.8.0-openjdk-portable-1.8.0.322.b06-4.portable.jre.el7.x86_64 ~/jres/java-8
Configure the
JAVA_HOME
environment variable:$ export JAVA_HOME=~/jres/java-8
Verify that
JAVA_HOME
environment variable is set correctly:$ printenv | grep JAVA_HOME JAVA_HOME=~/jres/java-8
NoteWhen installed using this method, Java will only be available for the current user.
Add the
bin
directory of the generic JRE path to thePATH
environment variable:$ export PATH="$JAVA_HOME/bin:$PATH"
Verify that
java -version
works without supplying the full path:$ java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)
NoteYou can ensure that
JAVA_HOME
environment variable persists for the current user by exporting the environment variable in~/.bashrc
.
2.3. Installing OpenJDK on RHEL by using yum
You can install OpenJDK using the system package manager, yum
.
Prerequisites
- Log in as a user with root privileges.
- Registered your local system to your Red Hat Subscription Management account. See the Registering a system using Red Hat Subscription Management user guide.
Procedure
Run the
yum
command, specifying the package you want to install:$ sudo yum install java-1.8.0-openjdk-devel
Check that the installation works:
$ javac -version javac 1.8.0_322
2.4. Installing OpenJDK on RHEL by using an archive
You can install OpenJDK with an archive. This is useful if the Java administrator does not have root privileges.
To ease upgrades, create a parent directory to contain your JREs and create a symbolic link to the latest JRE using a generic path.
Procedure
Create a directory to where you want to download the archive file, and then navigate to that directory on your command-line interface (CLI). For example:
$ mkdir ~/jdks $ cd ~/Downloads
- Navigate to the Software Downloads page on the Red Hat Customer Portal.
- Select the latest version of OpenJDK 8 from the Version drop-down list, and then download the JDK archive for Linux to your local system.
Extract the contents of the archive to a directory of your choice:
$ tar -xf java-1.8.0-openjdk-portable-1.8.0.322.b06-4.portable.jdk.el7.x86_64.tar.xz -C ~/jdks
Create a generic path by using symbolic links to your JDK for easier upgrades:
$ ln -s ~/jdks/java-1.8.0-openjdk-portable-1.8.0.322.b06-4.portable.jdk.el7.x86_64 ~/jdks/java-8
Configure the
JAVA_HOME
environment variable:$ export JAVA_HOME=~/jdks/java-8
Verify that
JAVA_HOME
environment variable is set correctly:$ printenv | grep JAVA_HOME JAVA_HOME=~/jdks/java-8
NoteWhen installed using this method, Java will only be available for the current user.
Add the
bin
directory of the generic JRE path to thePATH
environment variable:$ export PATH="$JAVA_HOME/bin:$PATH"
Verify that
java -version
works without supplying the full path:$ java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)
NoteYou can ensure that
JAVA_HOME
environment variable persists for the current user by exporting the environment variable in~/.bashrc
.
2.5. Installing multiple major versions of OpenJDK on RHEL by using yum
You can install multiple versions of OpenJDK using the system package manager, yum
.
Prerequisites
- A Red Hat Subscription Management (RHSM) account with an active subscription that provides access to a repository that provides the OpenJDK you want to install.
- You must have root privileges on the system.
Procedure
Run the following
yum
commands to install the package:For OpenJDK 17
$ sudo yum install java-17-openjdk
For OpenJDK 11
$ sudo yum install java-11-openjdk
For OpenJDK 8
$ sudo yum install java-1.8.0-openjdk
After installing, check the available java versions:
$ sudo yum list installed "java*" Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.322.b06-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-11-openjdk.x86_64 1:11.0.14.0.9-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-17-openjdk.x86_64 1:17.0.2.0.8-4.el8_5 @rhel-8-for-x86_64-appstream-rpms
Check the current java version:
$ java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)
NoteIf the output from the previous command shows that you have a different major version of OpenJDK checked out on your system, you can enter the following command in your CLI to switch your system to use OpenJDK 8:
$ sudo update-alternatives --config 'java'
Additional resources
- For more information about configuring the default Java version, see Non-interactively selecting a system-wide OpenJDK version on RHEL.
2.6. Installing multiple major versions of OpenJDK on RHEL by using an archive
You can install multiple major versions of OpenJDK by using the same procedures found in Installing a JRE on RHEL by using an archive or Installing OpenJDK on RHEL 8 by using an archive using multiple major versions.
For instructions how to configure the default OpenJDK version for the system, see Interactively selecting a system-wide OpenJDK version on RHEL.
Additional resources
- For instructions on installing a JRE, see Installing a JRE on RHEL using an archive.
- For instructions on installing a JDK, see Installing OpenJDK on RHEL using an archive.
2.7. Installing multiple minor versions of OpenJDK on RHEL by using yum
You can install multiple minor versions of OpenJDK on RHEL. This is done by preventing the installed minor versions from being updated.
Prerequisites
- Choose system-wide version of OpenJDK from Non-interactively selecting a system-wide OpenJDK version on RHEL.
Procedure
Add the
installonlypkgs
option in the/etc/yum.conf
directory to specify the OpenJDK packages thatyum
can install but not update.installonlypkgs=java-<version>--openjdk,java-<version>--openjdk-headless,java-<version>--openjdk-devel
Updates will install new packages while leaving the old versions on the system.
$ rpm -qa | grep java-1.8.0-openjdk java-1.8.0-java-1.8.0-openjdk-1.8.0.312.b07-2.el8_5.x86_64 java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5.x86_64
The different minor versions of OpenJDK can be found in the
/usr/lib/jvm/<minor version>
files.For example, the following shows part of
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0
:$ /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5.x86_64/bin/java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode) $ /usr/lib/jvm/java-1.8.0-java-1.8.0-openjdk-1.8.0.312.b07-2.el8_5.x86_64/bin/java -version openjdk version "1.8.0_312" OpenJDK Runtime Environment (build 1.8.0_312-b07) OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)
2.8. Installing multiple minor versions of OpenJDK on RHEL by using an archive
Installing multiple minor versions is the same as Installing a JRE on RHEL by using an archive or Installing OpenJDK on RHEL 8 by using an archive using multiple minor versions.
For instructions how to choose a default minor version for the system, see Non-interactively selecting a system-wide OpenJDK version on RHEL.
Additional resources
- For instructions on installing a JRE, see Installing a JRE on RHEL using an archive.
- For instructions on installing a JDK, see Installing OpenJDK on RHEL using an archive.
Chapter 3. Debug symbols for OpenJDK 8
Debug symbols help in investigating a crash in OpenJDK applications.
3.1. Installing the debug symbols
This procedure describes how to install the debug symbols for OpenJDK.
Prerequisites
Installed the
gdb
package on your local sytem.-
You can issue the
sudo yum install gdb
command on your CLI to install this package on your local system.
-
You can issue the
Procedure
To install the debug symbols, enter the following command:
$ sudo yum debuginfo-install java-1.8.0-openjdk $ sudo yum debuginfo-install java-1.8.0-openjdk-headless
These commands install
java-1.8.0-openjdk-debuginfo
,java-1.8.0-openjdk-headless-debuginfo
, and additional packages that provide debug symbols for OpenJDK 8 binaries. These packages are not self-sufficient and do not contain executable binaries.NoteThe
debuginfo-install
is provided by theyum-utils
package.To verify that the debug symbols are installed, enter the following command:
$ gdb
which java
Reading symbols from /usr/bin/java...Reading symbols from /usr/lib/debug/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5/bin/java-1.8.0.322.b06-2.el8_5.x86_64.debug...done. (gdb)
3.2. Checking the installation location of debug symbols
This procedure explains how to find the location of debug symbols.
If the debuginfo
package is installed, but you cannot get the installation location of the package, then check if the correct package and java versions are installed. After confirming the versions, check the location of debug symbols again.
Prerequisites
Installed the
gdb
package on your local sytem.-
You can issue the
sudo yum install gdb
command on your CLI to install this package on your local system. - Installed the debug symbols package. See Installing the debug symbols.
-
You can issue the
Procedure
To find the location of debug symbols, use
gdb
withwhich java
commands:$ gdb
which java
Reading symbols from /usr/bin/java...Reading symbols from /usr/lib/debug/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5/bin/java-1.8.0.322.b06-2.el8_5.x86_64.debug...done. done. (gdb)Use the following commands to explore the
*-debug
directory to see all the debug versions of the libraries, which includejava
,javac
, andjavah
:$ cd /usr/lib/debug/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5
$ tree OJDK 8 version: └── java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5 ├── bin │ ... │ │── java-java-1.8.0.322.b06-2.el8_5.x86_64.debug │ ├── javac-java-1.8.0.322.b06-2.el8_5.x86_64.debug │ ├── javadoc-java-1.8.0.322.b06-2.el8_5.x86_64.debug │ ... └── lib ├── jexec-java-1.8.0.322.b06-2.el8_5.x86_64.debug ├── jli │ └── libjli.so-java-1.8.0.322.b06-2.el8_5.x86_64.debug ├── jspawnhelper-java-1.8.0.322.b06-2.el8_5.x86_64.debug │ ...
The javac
and javah
tools are provided by the java-1.8.0-openjdk-devel
package. You can install the package using the command: $ sudo debuginfo-install java-1.8.0-openjdk-devel
.
3.3. Checking the configuration of debug symbols
You can check and set configurations for debug symbols.
To get the list of the installed packages, enter the following command:
$ sudo yum list installed | grep 'java-1.8.0-openjdk-debuginfo'
If some debug information packages have not been installed, enter the following command to install the missing packages:
$ sudo yum debuginfo-install glibc-2.28-151.el8.x86_64 libgcc-8.4.1-1.el8.x86_64 libstdc++-8.4.1-1.el8.x86_64 sssd-client-2.4.0-9.el8.x86_64 zlib-1.2.11-17.el8.x86_64
Run the following command if you want to hit a specific breakpoint:
$ gdb -ex 'handle SIGSEGV noprint nostop pass' -ex 'set breakpoint pending on' -ex 'break JavaCalls::call' -ex 'run' --args java ./HelloWorld
The above command completes the following tasks:
- Handles the SIGSEGV error as the JVM uses SEGV for stack overflow check.
-
Sets pending breakpoints to
yes
. -
Calls the break statement in
JavaCalls::call
function. The function to starts the application in HotSpot (libjvm.so).
3.4. Configuring the debug symbols in a fatal error log file
When a Java application is down due to a JVM crash, a fatal error log file is generated, for example: hs_error
, java_error
. These error log files are generated in current working directory of the application. The crash file contains information from the stack.
Procedure
You can remove all the debug symbols by using the
strip -g
command.The following code shows an example of non-stripped
hs_error
file:Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.so+0xb83d2a] Unsafe_SetLong+0xda j sun.misc.Unsafe.putLong(Ljava/lang/Object;JJ)V+0 j Crash.main([Ljava/lang/String;)V+8 v ~StubRoutines::call_stub V [libjvm.so+0x6c0e65] JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0xc85 V [libjvm.so+0x73cc0d] jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) [clone .constprop.1]+0x31d V [libjvm.so+0x73fd16] jni_CallStaticVoidMethod+0x186 C [libjli.so+0x48a2] JavaMain+0x472 C [libpthread.so.0+0x9432] start_thread+0xe2
The following code shows an example of stripped
hs_error
file:Stack: [0x00007ff7e1a44000,0x00007ff7e1b44000], sp=0x00007ff7e1b42850, free space=1018k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.so+0xa7ecab] j sun.misc.Unsafe.putAddress(JJ)V+0 j Crash.crash()V+5 j Crash.main([Ljava/lang/String;)V+0 v ~StubRoutines::call_stub V [libjvm.so+0x67133a] V [libjvm.so+0x682bca] V [libjvm.so+0x6968b6] C [libjli.so+0x3989] C [libpthread.so.0+0x7dd5] start_thread+0xc5
Enter the following command to check that you have the same version of debug symbols and the fatal error log file:
$ java -version
NoteYou can also use the
sudo update-alternatives --config 'java'
to complete this check.Use the
nm
command to ensure thatlibjvm.so
has ELF data and text symbols:$ nm /usr/lib/debug/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-2.el8_5/lib/server/libjvm.so-1.8.0.322.b06-2.el8_5.x86_64.debug
Additional resources
-
The crash file
hs_error
is incomplete without the debug symbols installed. For more information, see Java application down due to JVM crash.
Chapter 4. Updating OpenJDK 8 on RHEL
The following sections provide instructions for updating OpenJDK 8 on RHEL.
4.1. Updating OpenJDK 8 on RHEL by using yum
The installed OpenJDK packages can be updated using the yum
system package manager.
Prerequisites
- You must have root privileges on the system.
Procedure
Check the current OpenJDK version:
$ sudo yum list installed "java*"
A list of installed OpenJDK packages displays.
Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.322.b06-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-11-openjdk.x86_64 1:11.0.14.0.9-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-17-openjdk.x86_64 1:17.0.2.0.8-4.el8_5 @rhel-8-for-x86_64-appstream-rpms
Update a specific package. For example:
$ sudo yum update java-1.8.0-openjdk
Verify that the update worked by checking the current OpenJDK versions:
$ java -version openjdk version "1.8.0_322" OpenJDK Runtime Environment (build 1.8.0_322-b06) OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)
NoteIf the output from the previous command shows that you have a different major version of OpenJDK checked out on your system, you can enter the following command in your CLI to switch your system to use OpenJDK 8:
$ sudo update-alternatives --config 'java'
4.2. Updating OpenJDK 8 on RHEL by using an archive
You can update OpenJDK using the archive. This is useful if the OpenJDK administrator does not have root privileges.
Prerequisites
-
Know the generic path pointing to your JDK or JRE installation. For example,
~/jdks/java-8
Procedure
Remove the existing symbolic link of the generic path to your JDK or JRE.
For example:
$ unlink ~/jdks/java-8
- Install the latest version of the JDK or JRE in your installation location.
Additional resources
- For instructions on installing a JRE, see Installing a JRE on RHEL using an archive.
- For instructions on installing a JDK, see Installing OpenJDK on RHEL using an archive.
Revised on 2022-03-14 16:59:12 UTC