Eclipse OpenJ9 version 0.15 release notes
These release notes support the Eclipse OpenJ9 0.15 release plan.
Binaries and supported environments
OpenJ9 release 0.15 supports OpenJDK 8, 11, and 12. Binaries are available at the AdoptOpenJDK project:
All builds are tested against the OpenJ9 functional verification (FV) test suite, the OpenJDK test suites, and additional tests at AdoptOpenJDK.
To learn more about support for OpenJ9 releases, including OpenJDK levels and platform support, see Supported environments.
Notable changes in this release
The following table covers notable changes in v0.15. Further information about these changes can be found in the user documentation.
| Issue number |
Description |
Version / Platform |
Impact |
| #5598 |
Performance improvements for JVMTI watched fields by default |
OpenJDK8 and later (x86, Linux on Z, and z/OS only) |
Following successful results, the experimental -XX:[+|-]JITInlineWatches option is now enabled by default, providing
performance improvements for JVMTI watched fields on x86 systems. Support is also extended from x86 to Linux on Z, and z/OS. |
| #5183 |
Extended platform support for software-based pause-less garbage collection |
OpenJDK8 and later (IBM Z systems) |
Reduced garbage collection pause times when using -Xgc:concurrentScavenge with the gencon GC policy for Linux on Z systems. |
| #164 |
ChaCha20 algorithm support |
OpenJDK11 only |
On Java 11, ChaCha20 and ChaCha20-Poly1305 algorithms can now use OpenSSL. |
| #59 |
System property jdk.nativeDigest has no effect |
OpenJDK8 and later |
The Digest algorithm is now disabled for JDK 12 due to #5611. The algorithm was disabled in JDK 8 and 11 in Eclipse OpenJ9 release 0.14.2. The system property jdk.nativeDigest cannot be used to enable the use of the Digest algorithm with OpenSSL. |
| #54 |
OpenJ9 now supports all POSIX signals listed in SunMiscSignalTest.java. |
OpenJDK8 and later |
Earlier release notes reported gaps in signal handling support, which are now resolved in this release. |
| #5293 |
Compatibility support for -XX:OnOutOfMemoryError |
OpenJDK8 and later |
For compatibility with HotSpot, this option can now be used to run a command or list of commands when a
java.lang.OutOfMemoryError exception occurs. |
| #6013 |
Support for Transparent HugePage allocation |
OpenJDK8 and later |
The VM now supports Transparent HugePage on Linux when you use the madvise (/sys/kernel/mm/transparent_hugepage/enabled) setting. |
| #5538 |
New jmap tool |
OpenJDK8 and later |
For compatibility, OpenJ9 includes an independent implementation of the jmap tool, which
prints statistics about classes on the heap, including number of objects and aggregate size. |
| #2679 |
JEP 331 is implemented |
OpenJDK11 and later |
An implementation of JEP 331 (Low-Overhead Heap Profiling) is now available. Restrictions are detailed in the user documentation. |
| #5882 |
-Xdiagnosticscollector option removed |
OpenJDK8 and later |
No impact. Redundant option removed. |
| #5374 |
New heuristics to implement compaction during idle garbage collection |
OpenJDK8 and later |
Heuristics are added to automatically compact the heap during idle garbage collection (GC) processing. Therefore, if
-XX:+IdleTuningGCOnIdle is enabled, compaction might occur. To force compaction every time idle GC operations take place,
-XX:+IdleTuningCompactOnIdle must be enabled. |
| #5374 |
Change in shared classes behavior for checking timestamps of jar or zip files |
OpenJDK8 and later |
In earlier releases, the shared classes cache checks timestamps of jar or zip files every time a class is loaded and reloads a class if the timestamp has changed. This behavior is now changed; timestamps are checked only when zip or jar files are added to class loaders and used for the first time to look for a class.
To revert to the behavior of earlier releases, set the -Xshareclasses:checkURLTimestamps option on the command line when you start your application. |
| #6059 |
Automatically setting an initial heap size |
OpenJDK8 and later |
OpenJ9 can now learn and set an appropriate initial heap size for an application as an alternative to a user manually sizing and setting an -Xms value. The VM records the size of the heap when startup processing ends, writing this data to the shared classes cache. An average value is set over a few restarts, helping to ensure that the value used for the initial heap size is as accurate as possible. See the -XX:[+|-]useGCStartupHints option (disabled by default). The hint
recorded is specific to the application command line. |
Known Issues
The v0.15.1 release contains the following known issues and limitations:
| Issue number |
Description |
Platform |
Impact |
Workaround |
| #5533 |
Attach API internal interfaces have changed slightly, affecting both the JDK's internal class library and tools.jar |
Java 8: all platforms |
If an application uses a private copy of tools.jar, the application might be unable to use the attach API if it is using a newer JDK, because the Java classes will not match. |
Use the tools.jar from the newer JDK. |
| #2507 |
Restriction analyzing system (core) dumps |
Linux and Windows |
You must use a 32-bit JVM to look at a 32-bit core, and a 64-bit JVM to look at a 64-bit core. This restriction will be fixed in a later version of OpenJ9. |
None |
| #479 |
Non-compressed references VM builds not available |
AIX, Linux on Z, Linux on Power |
Non-compressed references VM builds, which support heaps larger than 57GB, are built on Linux on x86, Windows, and macOS. |
Manual builds on other platforms are possible by following our detailed build instructions. |
| #897 |
Javadoc not building some OpenJ9 extensions. |
All platforms |
Some API documentation is missing in the build/<platform>/docs directory. |
None |
| #898 |
Javadoc building some unsupported OpenJ9 extensions. |
All platforms |
Some API documentation in build/<platform>/docs is not supported with OpenJ9. |
None |
Other changes
A full commit history for this release is available at Eclipse OpenJ9 v0.15.1.
