IBM SDK, Java Technology Edition, Version 7 Release 1: Supplementary documentation

Note: java.nio.charset classes already used the correct mappings and are unaffected.

If you require the previous mappings, specify the -Dibm.useCp970=true system property on the command line when you run your application.

In addition, the following characters from the KS X 1001 standard have been added:

Service refresh 4 fix pack 20 (January 2018)

Out of memory exceptions when running applications with compressed references enabled

The Oracle CPU for January contains an update for CVE-2018-2582 to fix vulnerabilities in the Hotspot virtual machine (VM) that might be exploited by Java web start applications and applets. Fixes are also applied for the OpenJ9 virtual machine. The fix increases the amount of low memory used for VMs that use compressed references. Customers who are running close to the maximum amount of allowed 32-bit memory might experience out of memory exceptions. A possible workaround is to use the -Xmcrs option to secure space in the lowest 4GB memory area for any native classes, monitors, and threads that are used by compressed references.

For more information about this option, see -Xmcrs .

Service refresh 4 fix pack 10 (October 2017)

Support for z/OS v2.3

This update includes support for z/OS v2.3.

Service refresh 4 fix pack 1 (February 2017)

Security vulnerability CVE-2016-2183

A further fix is added to mitigate against this vulnerability, which is described here . (APAR IV93288)

Go back to top

Service refresh 3 fix pack 10 (July 2015)

Partial fix for change in behavior for -Xshareclasses:destroyAll

In service refresh 2 fix pack 10, a behavior change was reported for this option on z/OS platforms. See Change in behavior for -Xshareclasses:destroyAll .

Following a fix for the 64-bit JVM, the problem remains only on the 31-bit JVM. When the destroyAll option is invoked from a 31-bit JVM, 64-bit caches are not destroyed. The following message is displayed:

JVMSHRC735I Use a 64-bit JVM to perform the requested operation on the 64-bit shared cache \"cachename\" as the 31-bit JVM cannot verify that the shared memory was created by the JVM

Service refresh 3 (May 2015)

DumpControlMXBean visible in JConsole

The DumpControlMXBean is unintentionally visible in JConsole. Do not use this MXBean to create heap, system, or Java dumps. Instead, use the Health Center tool as described in Triggering Dumps .

Service refresh 2 fix pack 10 (February 2015)

Change in behavior for -Xshareclasses:destroyAll

Due to a current issue on z/OS, when the destroyAll option is invoked from a 31-bit Java virtual machine (JVM), 64-bit caches are not removed. Similarly, when the destroyAll option is invoked from a 64-bit JVM, 31-bit caches are not removed. The following message is displayed:


JVMSHRC735I: Use a nn-bit JVM to perform the requested operation on the nn-bit shared cache \"cachename\" as the nn-bit JVM cannot verify that the shared memory was created by the JVM.

Go back to top

Installable packages

When you download and install packages for this release, you can choose a language in which to review and accept the license. On AIX® or Linux (InstallAnywhere) archive packages, there is no option to review the license in Lithuanian even though a Lithuanian license exists in the package. You must choose an alternative language during installation and then review the contents of the Lithuanian license, which can be found in the docs/lt directory.

Co-existence of releases

IBM SDK, Java Technology Edition Version 7 Release 1 can co-exist with IBM SDK, Java Technology Edition Version 7 on the same Windows operating system. However, if the first installation is removed, the Windows registry is corrupted and the following error is seen when you run the java -version command:

    Error: Failed reading value of registry key:
    Software\IBM\Java2 Runtime Environment\CurrentVersion
    Error: could not find java.dll
    Error: Could not find Java SE Runtime Environment.

This problem occurs when the second installation is installed as the system or non-system JVM. In this situation, you can obtain version information by specifying the full installation path when you run the java -version command.

Go back to top