Service refresh 1

Understand the changes that are implemented in service refresh 1 and later fix packs.

Skip to Service refresh 1 fix pack 10

Service refresh 1

This service refresh provides performance enhancements and serviceability improvements. There is also a change in default behavior for applets and Web Start applications.

Support for new operating systems (Linux® only)

Support for Red Hat Enterprise Linux 7.1 is now available with this release. For a list of supported operating systems, see Supported environments.

Change to applet or Web start application behavior (AIX®, Linux, and Windows only)

When an applet or Web Start application is started, a warning is displayed if a later release of the runtime environment is available that contains security updates. A user can choose to continue or block the application from continuing. If the runtime environment is unable to determine whether a later release is available, a similar warning message is shown if the runtime environment is more than six months old.

Changes to InstallAnywhere unattended installation

If you use an existing response file to install packages without user intervention, you must include the line LICENSE_ACCEPTED=TRUE in the response file to indicate that you have read the terms of the license agreement and confirm your acceptance. This line is automatically added if you create a new response file by using the attended installation process. For more information, see Installing from an InstallAnywhere package (AIX and Linux only).

Hardware compression acceleration is available on Little Endian Power Systems and IBM Z systems (Linux only)
You can now use hardware compression acceleration on Little-Endian Power Systems and IBM Z systems with the following operating systems:
  • SUSE Linux Enterprise Server for System z® 12
  • Red Hat Enterprise Linux 7.1 for 64-bit Power Systems (Little Endian)
For more information, see Enabling hardware compression acceleration (AIX, Linux only).
Runtime Instrumentation (RI) facility (Linux and AIX only)
The RI facility is a feature that is available in Power® 8, zEC12, and later processors that offers hardware support for collecting profiling information at run time. The process uses minimal resources. The JVM uses the RI facility by default on all platforms that support it. For more information about controlling the use of the RI facility, see -XX:[+|-]RuntimeInstrumentation (AIX, Linux only).
Note: Due to the current Linux kernel implementation, a user cannot reliably profile a Java application when RI is enabled on IBM Power systems. If you want to use system profilers like oprofile or perf, you must turn off the use of the RI facility.
Additional support for saving and restoring non-persistent shared caches (AIX, Linux, and z/OS® only)

You can now create a snapshot file of a non-persistent shared cache. After the next IPL, the snapshot file is used to restore a copy of the non-persistent cache into shared memory. When snapshot files are no longer required, you can remove them. The following suboptions have been added to the -Xsharedclasses command line option:

snapshotCache
Creates a snapshot file of an existing non-persistent shared cache.
restoreFromSnapshot
Restores a new non-persistent shared cache from a snapshot file.
destroySnapshot
Destroys a specific shared cache snapshot.
destroyAllSnapshots
Destroys all available shared cache snapshots.

For more information, see -Xshareclasses option.

New methods in the CUDA4J API (Linux only)
The CUDA4J API contains the following new methods. These methods enable you to specify java.lang.Object instances when you create a Parameters object or launch a kernel:
  • In class CudaKernel: public final void launch(CudaGrid grid,java.lang.Object... parameters)
  • In class CudaKernel.Parameters: Parameters(java.lang.Object... values)
The CUDA4J application programming interface (API) is used to develop applications that specify when to use the graphics processing unit (GPU) for application processing. For more information, see The CUDA4J application programming interface.

Service refresh 1 fix pack 10

This service refresh includes serviceability improvements.

Invalidating AOT methods in the shared classes cache
You can now invalidate failing AOT methods in the shared classes cache to prevent them being loaded without destroying and re-creating the cache. Three new -Xshareclasses suboptions are available to find (findAotMethods), invalidate (invalidateAotMethods), or revalidate (revalidateAotMethods) these methods. For more information, see -Xshareclasses option.
Support for Windows 10
Microsoft Windows 10 is now supported.