IBM SDK, Java Technology Edition, Version 7 Release 1: Current news
Support information for IBM® SDK, Java™ Technology Edition, Version 7 Release 1 that is not available in the user documentation.
The documentation to support this release is available in the online product documentation.
Supplementary information is available for the following updates:
- Service refresh 4 fix pack 5
- Service refresh 4 fix pack 1
- Service refresh 3 fix pack 10
- Service refresh 3
- Service refresh 2 fix pack 10
For information about the daylight saving time changes included in this release, see Olson time zone updates. Later updates can by applied using the IBM Time Zone Update Utility for Java (JTZU).
To compare the IBM SDK functionality with Oracle build levels at each service refresh level, see Comparative Oracle build levels.
You can download the SDK from developerWorks.
Service refresh 4 fix pack 5 (April 2017)
EC with keys less than 224 bits are disabled
The following two properties are updated to prevent the use of EC keys with less than 224 bits:
jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768, 3DES_EDE_CBC, DESede, EC keySize < 224
EC curves weaker than 256 bits are removed from the default enabled list
The following list shows curves that are enabled by default:
// NIST curves
// Non-FIPS curves
A new system property is available to define a list of enabled curves.
jdk.tls.namedGroups="secp521r1, secp256r1, secp384r1"
The values for named curves must be separated with a comma.
If the system property is not defined or the value is empty, the default
curves and preferences are used.
Go back to top
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)
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.
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.
Comparative Oracle build levels
The following table indicates the Oracle FCS build level that has comparative functionality to the IBM SDK:
|Release date||IBM SDK 7 Release 1||Oracle Java 7 FCS build|
|December 2013||Initial release||Update 45 Build 18|
|April 2014||Service refresh 1||Update 55 Build 13|
|July 2014||Service refresh 1 fix pack 1||Update 65 Build 19|
|November 2014||Service refresh 2||Update 71 Build 13|
|February 2015||Service refresh 2 fix pack 10||Update 75 Build 13|
|May 2015||Service refresh 3||Update 79 Build 14|
|July 2015||Service refresh 3 fix pack 10||Update 85 Build 15|
|November 2015||Service refresh 3 fix pack 20||Update 91 Build 15|
|January 2016||Service refresh 3 fix pack 30||Update 95 Build 12|
|April 2016||Service refresh 3 fix pack 40||Update 101 Build 14|
|July 2016||Service refresh 3 fix pack 50||Update 111 Build 13|
|October 2016||Service refresh 3 fix pack 60||Update 121 Build 15|
|February 2017||Service refresh 4 fix pack 1||Update 131 Build 12|
|April 2017||Service refresh 4 fix pack 5||Update 141 Build 11|
More support for:
Runtimes for Java Technology
Software version: 7.1
Operating system(s): AIX, IBM i, Linux, Windows, z/OS
Software edition: Java SE
Reference #: 1639279
Modified date: 20 July 2015
Translate this page: