Release notes for Red Hat build of OpenJDK 11.0.14

Red Hat build of OpenJDK 11

Red Hat Customer Content Services


This document provides an overview of new features in Red Hat build of OpenJDK 11 and a list of potential known issues and possible workarounds.


Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of Red Hat build of OpenJDK is available in three versions: Red Hat build of OpenJDK 8u, Red Hat build of OpenJDK 11u, and Red Hat build of OpenJDK 17u.

Packages for the Red Hat build of 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.

Providing feedback on Red Hat build of OpenJDK documentation

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.


  1. Click the following link to create a ticket.
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

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.

Chapter 1. Support policy for Red Hat build of OpenJDK

Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these are the same versions that Oracle designates as long-term support (LTS) for the Oracle JDK.

A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy.


RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration.

Chapter 2. Differences from upstream OpenJDK 11

Red Hat build of OpenJDK in Red Hat Enterprise Linux (RHEL) contains a number of structural changes from the upstream distribution of OpenJDK. The Microsoft Windows version of Red Hat build of OpenJDK attempts to follow RHEL updates as closely as possible.

The following list details the most notable Red Hat build of OpenJDK 11 changes:

  • FIPS support. Red Hat build of OpenJDK 11 automatically detects whether RHEL is in FIPS mode and automatically configures Red Hat build of OpenJDK 11 to operate in that mode. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
  • Cryptographic policy support. Red Hat build of OpenJDK 11 obtains the list of enabled cryptographic algorithms and key size constraints from RHEL. These configuration components are used by the Transport Layer Security (TLS) encryption protocol, the certificate path validation, and any signed JARs. You can set different security profiles to balance safety and compatibility. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
  • Red Hat build of OpenJDK on RHEL dynamically links against native libraries such as zlib for archive format support and libjpeg-turbo, libpng, and giflib for image support. RHEL also dynamically links against Harfbuzz and Freetype for font rendering and management.
  • The file includes the source for all the JAR libraries shipped with Red Hat build of OpenJDK.
  • Red Hat build of OpenJDK on RHEL uses system-wide timezone data files as a source for timezone information.
  • Red Hat build of OpenJDK on RHEL uses system-wide CA certificates.
  • Red Hat build of OpenJDK on Microsoft Windows includes the latest available timezone data from RHEL.
  • Red Hat build of OpenJDK on Microsoft Windows uses the latest available CA certificate from RHEL.

Additional resources

Chapter 3. Red Hat build of OpenJDK release notes

Review the following release notes to understand changes from this Red Hat build of OpenJDK 11.0.14 patch release:

3.1. Resolved connection issue

The Red Hat build of OpenJDK release resolves an issue that was identified when using the Java HTTP client,, to connect to the URL. This issue persisted on the Red Hat build of OpenJDK build for Microsoft Windows and on the Red Hat build of OpenJDK build for RHEL.

The initial Red Hat build of OpenJDK 11.0.14 release contained a regression that was introduced by improvements to the HTTP client. This regression caused both the :authority and the Host header fields to be sent in HTTP/2 requests, which are rejected by some HTTP servers, such as Google’s server. When you attempted to establish this connection, you would receive an exception message. This exception message would indicate that the Java HTTP client could not successfully communicate by using the HTTP/2 protocol.

Example of an exception message when attempting to connect to with

java.util.concurrent.ExecutionException: Received RST_STREAM: Protocol error

The Red Hat build of OpenJDK release resolves the issue by reverting to the original behavior of only setting the :authority header field to be sent in an HTTP/2 request.

For more information about this issue and how it was resolved, see JDK-8218546 and see the advisories related to the Red Hat build of OpenJDK release.

Chapter 4. Red Hat build of OpenJDK features

The latest Red Hat build of OpenJDK 11 release might include new features. Additionally, this latest release might enhance, deprecate, or remove features that originated from previous Red Hat build of OpenJDK 11 releases.


For all the other changes and security fixes, see OpenJDK 11.0.14 Released.

4.1. New features and enhancements

Review the following release notes to understand new features and feature enhancements that have been included with the Red Hat build of OpenJDK 11.0.14 release:

Archive file system provider

For Red Hat build of OpenJDK 11.0.14, the archive file system provider rejects existing archive files with file name elements that include a dot (.) or two dots (..). If you attempt to use existing archive files that include these named elements as system files, and you invoke the java.nio.file.FileSystems.newFileSystem(…​) method, the method throw a ZipException error message on your command-line interface.

For more information about the change to the archive file system provider, see JDK-8271517.

IANA Time Zone Database

The Internet Assigned Numbers Authority (IANA) updated its Time Zone Database to version 2021c. Red Hat OpenJDK date and time libraries depends on IANA’s Time Zone Database for determining local time for various regions around the world.


The 2021b release of the Time Zone Database updated time zone rules that existed before 1970. For more information about the 2021b release, see 2021b release of tz code and data available on the IANA website.

For more information about IANA’s Time Zone Database, see Time Zone Database on the IANA website.

For more information about IANA’s 2021c Time Zone Database release, see JDK-8274857.

OpenJDK’s identification of Microsoft Windows versions

Before the Red Hat build of OpenJDK 11, the system property that is retrieved from System.getProperty() and the HotSpot error logs would report Windows 10.0 on Microsoft Windows 11 and Windows Server 2019 on Microsoft Windows Server 2022. Red Hat build of OpenJDK now identifies the correct version on these systems.

New option for the GC.heap_dump diagnostic command

Red Hat build of OpenJDK 11.0.14 adds the gz integer option to the GC.heap_dump diagnostic command of the jcmd utility.

You can use this option to enable gzip compression and to set a compression level when creating a heap dump. Compression level values range from 1 through 9, with the value of 1 as the fastest setting and the value of 9 as the slowest setting.

For more information about the gz integer option, see JDK-8250554.

Microsoft Windows version

Red Hat build of OpenJDK that runs on either Microsoft Windows 11 or Microsoft Windows Server 2022 now displays the correct Microsoft Windows version in the value of the System.getProperty() system property and any HotSpot error logs. Before the Red Hat build of OpenJDK 11.0.14 release, this behavior was not possible if you updated your Microsoft Windows operating system or Microsoft Windows Server to a later version.

System properties for disabling TLS extensions

You can use two new system properties to disable Transport Layer Security (TLS) extensions for the TLS protocol. These system properties are detailed as follows:

  • jdk.tls.client.disableExtensions that disables TLS extensions used by TLS clients.
  • jdk.tls.server.disableExtensions that disables TLS extensions used by TLS servers.

A disabled TLS extension does not form part of a TLS handshake process. You must not disable mandatory TLS extensions, because these TLS extensions are essential for establishing a TLS handshake.

Both system properties ignore duplicated, misspelled, unknown, and unsupported TLS extension names. Extension names must conform to the Internet Assigned Numbers Authority (IANA) specification.

For more information about these new system properties, see JDK-8260310.

For more information about the TLS extensions that comply with the IANA specification, see Transport Layer Security (TLS) Extensions on the IANA website.

SunPKCS11 provider configuration attributes

The SunPKCS11 provider includes new configuration attributes that enhance the usage of native resources, such as key objects. The SunPKCS11 provider must use native resources for it to work with native PKCS11 libraries.

Table 4.1. New SunPKCS11 provider configuration attributes








For more information about the new SunPKCS11 provider configuration attributes, see JDK-8272907.

4.2. Deprecated and removed features

Review the following release notes to understand pre-existing features that have been either deprecated or removed in the Red Hat build of OpenJDK 11.0.14 release:

Google GlobalSign root certificate

Red Hat build of OpenJDK 11.0.14 removes the following root certificate from the cacerts keystore:

Alias name
globalsignr2ca [jdk]
Distinguished name
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R2

For more information about this removed Google GlobalSign root certificate, see JDK-8272535.

Chapter 5. Advisories related to this release

The following advisories have been issued to bugfixes and CVE fixes included in this release.

Revised on 2024-05-09 16:46:44 UTC

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.