Support Information for IBM® SDK, Java™ Technology Edition, Version 7 that is not available in the user documentation.
The documentation to support this release is available in online product documentation.
Supplementary information is available for the following updates:
- Service refresh 9 fix pack 30
- Service refresh 9 fix pack 20
- Service refresh 9 fix pack 10
- Service refresh 9 fix pack 1
- Service refresh 8 fix pack 10
- Service refresh 6 fix pack 1
- Service refresh 6
- Service refresh 4 fix pack 2
- Service refresh 4 fix pack 1
- Service refresh 3
- Initial release of IBM SDK, Java Technology Edition, Version 7
To compare the IBM SDK functionality with Oracle build levels at each service refresh level, see Comparative Oracle build levels.
For information about security fixes, see Security Alerts.
For a list of the IBM fixes included, see IBM SDK, Java Technology Edition, Version 7 fixes.
To download the latest service refresh, see IBM developer kits.
For information about the daylight saving time changes included in service refreshes and fix pack levels, see Olson time zone updates. Later updates can by applied using the IBM Time Zone Update Utility for Java (JTZU).
Service refresh 9 fix pack 30 (January 2016)
Change to default behavior for memory protection of a shared classes cache
On Linux and Windows systems, new options are available to protect partially filled pages in the shared classes cache. These options prevent accidental memory overwrites, which can cause cache corruption. After the startup phase, a VM now protects partially filled pages by default. For more information about these options and the default setting, see the mprotect sub option in the -Xshareclasses topic.
Service refresh 9 fix pack 20 (Nov 2015)
If your application takes untrusted XML, XSD or XSL files as input, you can enforce specific limits during JAXP processing to protect your application from malformed data. This option can be specified on the command line to limit the length of XML names in XML documents.
Where value is a positive integer. A value of 0 or a negative number sets no limits. The default value is 0.
You can also set this limit by adding the following line to your jaxp.properties file:
Service refresh 9 fix pack 10 (July 2015)
Partial fix for change in behavior for -Xshareclasses:destroyAll
In service refresh 8 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 9 fix pack 1 (June 2015)
Logjam security vulnerability
A potential weakness is exposed with DH and DHE cipher suites that relates to the Logjam security vulnerability. A fix is provided to address this issue. For more information, see IBM SDK, Java Technology Edition: Fix packs to address the Logjam security vulnerability (CVE-2015-4000)
Service refresh 8 fix pack 10 (February 2015)
JCE FIPS guide
The certified JCE FIPS guide can be found here: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1993.pdf
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.
Service refresh 6 fix pack 1 (January 2014)
Default behaviour change when running unsigned or self-signed applets
Unsigned or self-signed applets no longer run by default because the security settings are changed to high. If you want to run unsigned or self-signed applets, you must change the security settings to medium. You can make this change in the Java Control Panel. Select the Security tab and move the slider to adjust the security level. This behavior change is not applicable to z/OS® or Linux on system Z platforms.
Service refresh 6 (October 2013)
Support for Windows Server 2012 R2
From this release of the SDK, Windows Server 2012 R2 is a supported environment on x86-64 platforms. The supported environments page in the user documentation is currently incorrect and will be corrected.
Service refresh 4 fix pack 2 (May 2013)
This fix pack includes a change to the default value for the RMI property java.rmi.server.useCodebaseOnly from false to true, which might cause unexpected errors for applications that use RMI. For more information, see http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/enhancements-7.html.
On Windows, improvements are made to the way that Runtime.exec decodes command strings. However, applications specifying commands that contain spaces in the program name, or that use quotation marks incorrectly, might fail to start. For more information, including guidance on resolving problems, see http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#jaruntime.
Service refresh 4 fix pack 1 (April 2013)
This fix pack contains a security fix for the Oracle security vulnerability,CVE-2013-0169. For any further security fixes in this release, see Security alerts.
Service refresh 3 (November 2012)
PKCS11 security provider
A new library is available that allows the IBMPKCS11Impl provider to run on the Linux AMD64 platform.
IBM SDK for Java Version 7 initial release (September 2011)
The SDK is functionally equivalent to the Oracle FCS version of Java 7 b147 for all distributions except Solaris, which is b148.
The z/OS® 31-bit and 64-bit SDKs are supported on z/OS 1.13.
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||Oracle Java 7 FCS build|
|September 2011||Initial release||Build 147|
|May 2012||Service Refresh 1||Update 3 Build 5|
|September 2012||Service Refresh 2||Update 3 Build 5|
|November 2012||Service Refresh 3||Update 6 Build 17|
|February 2013||Service Refresh 4||Update 13 Build 8|
|July 2013||Service Refresh 5||Update 25 Build 12|
|November 2013||Service Refresh 6||Update 45 Build 18|
|January 2014||Service Refresh 6 Fix Pack 1||Update 51 Build 11|
|April 2014||Service Refresh 7||Update 55 Build 13|
|July 2014||Service Refresh 7 Fix Pack 1||Update 65 Build 19|
|November 2014||Service Refresh 8||Update 71 Build 13|
|February 2015||Service Refresh 8 Fix Pack 10||Update 75 Build 13|
|May 2015||Service Refresh 9||Update 79 Build 14|
|July 2015||Service Refresh 9 Fix Pack 10||Update 85 Build 15|
|November 2015||Service Refresh 9 Fix Pack 20||Update 91 Build 15|
|January 2016||Service Refresh 9 Fix Pack 30||Update 95 Build 12|