Backport issue JDK-8208172 which allows for NULL messages in class resolution errors.
22.08.200.0
22.08.200.0
Release date: November 15, 2022
This release is based on Azul Prime 22.08.101.0 and corresponds to the following OpenJDK versions:
| Major Version | OpenJDK Version |
|---|---|
8 |
8u352 |
11 |
11.0.17 |
13 |
13.0.13 |
15 |
15.0.9 |
17 |
17.0.5 |
What’s New
-
Internal bug fixes.
-
October 2022 PSU release security fixes
-
Important information regarding Java in containers (Docker, Kubernetes, and related) about automatic thread pool size calculation and number of CPUs available to the application:
While in the general October 2022 release of Java 11 and 17, the default calculation of available CPU cores has changed in container environments following JDK-8281181, this change wasn’t made in the Azul Prime stable release 22.08.200.0 to allow seamless transition from previous stable versions.
That means, Azul Prime 22.08 differs in this aspect from current OpenJDK. In practical use, this difference will only affect those situations where a new migration from OpenJDK to Prime 22.08 is started. If you notice your application performance being affected during such a transition from OpenJDK to Prime 22.08 add
-XX:-UseContainerCpuSharesto the Java command line to switch Azul Prime to the same new calculation method as OpenJDK.To check your environment in general about this change, independent of whether it is running on OpenJDK or Azul Prime, run the following command inside your container to display the actual result of the available CPU number calculation:
Save the following code to file AvailableCPUs.java:
public class AvailableCPUs { public static void main(String[] args) { System.out.println("CPUs: " + Runtime.getRuntime().availableProcessors()); } }Run it:
java -showversion AvailableCPUs.java