IBM SDK, Java Technology Edition, Version 7 Release 1: Current news

News


Abstract

Support information for IBM® SDK, Java™ Technology Edition, Version 7 Release 1 that is not available in the user documentation.

Content

The documentation to support this release is available in IBM Knowledge Center.

Supplementary information, including late breaking news, is included in this support document.


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.



Language Environment run time options that cause ABENDs

If the Language Environment® run time option TERMTHDACT is set to UAIMM, unexpected 0C7 ABENDs might be reported. Although the ABENDs are reported, the JVM continues to run successfully. However, if the Language Environment run time option ERRCOUNT is set to a value greater than zero, the JVM might end when the value you specify for ERRCOUNT is reached. This behavior is seen on 31-bit and 64-bit environments. To work around this problem, run the JVM with the -Xjit:noResumableTrapHandler option.

To override the system-wide TERMTHDACT setting, you can pass a Language Environment parameter in your batch job without the UAIMM option, for example:
    // LEPARM='TERMTHDACT(TRACE,CESE,00000096),ERRCOUNT(0)'

Multitenancy feature

This feature is a technology preview. The following limitations apply when you are using the -Xmt option:
    JAVA_TOOLS_OPTIONS environment variable
      Setting parameters with the JAVA_TOOLS_OPTIONS environment variable is not supported.
    Specifying the -Djavad.home option
      If you specify the -Djavad.home option after the target class, it will be parsed incorrectly as an option, instead of an argument to the program.
      If you specify multiple instances of the -Djavad.home option, the first instance takes precedence. This behavior is incorrect; the final instance should take precedence, as is the convention with other conflicting command-line options.
    Adding options to the javad.options file
      When you add options to the javad.options file, each option must be on a separate line. Combining multiple options on the same line does not work.
    Specifying options on the command line
      If you specify options that are not valid on the command line, the options are silently ignored and the JVM continues to start.
    Obtaining information for each tenant, by using JMX
      When using API methods such as memoryBean.getHeapMemoryUsage() in a tenant, you might not get a value for each tenant. Depending on the API you use, and the method in which it is called, you might get either a value for the specific tenant, or a value for the entire javad process.
    Failure to call the close() method on a WatchService instance can result in tenant not shutting down
      If an application uses the java.nio.file.WatchService class but fails to call the close() method before the application ends, thread resources might not be cleaned up completely. If the resources are not cleaned up completely, the tenant does not shut down.
    Disk IO performance degradation when using the -Xlimit:diskIO option
      Use of the -Xlimit:diskIO resource control feature affects the speed of read and write operations to disk when very small amounts of data are being written. For example, if your application makes continuous write operations of one byte at a time by using the FileOutputStream.write method, there is a noticeable performance degradation. However, this performance degradation is not noticeable if you instead write 4 KB at a time.
    Network throughput degradation when using the -Xlimit:netIO option
      Use of the -Xlimit:netIO resource control feature might result in 10% to 20% network throughput degradation for both regular and datagram sockets, depending on the length of data that is read or written. For example, if your application makes continuous write operations of a few bytes at a time, you might see this impact on throughput.
    ResourceConsumptionException received when using the -Xlimit:threads option
      If your application uses the -Xlimit:threads option and the AsyncIO API is used, the threads started by the AsyncIO API are included in the limit. The result is that your application might receive a ResourceConsumptionException if too small a limit was specified.

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 Windows (Installshied) packages, and 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.

Known problem with zEDC

As per the specification of the java.util.zip.Deflater.setlevel() API, the deflate() API must not compress the data if the level is set to zero. However, with zEDC hardware compression, the deflate() API does compress the data when java.util.zip.Deflater.setlevel(0) is set. You can work around this problem by switching to software compression on z/OS®, which can be achieved by using one of these methods:
  • Set the z/OS environment variable _HZC_COMPRESSION_METHOD, by specifying the following command: export _HZC_COMPRESSION_METHOD=software
  • Disable the zEDC hardware adapter by making it offline.
  • Remove READ ACCESS to resource class FPZ.ACCELERATOR.COMPRESSION, which is a System Authorization Facility (SAF) FACILITY that protects access to the zEnterprise® Data Compression Express® coprocessor.

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.

-Xzero option

This option is deprecated and will be removed from future releases.

Go back to top



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 7 Update 45 Build 18
April 2014 Service refresh 1 7 Update 55 Build 13
July 2014 Service refresh 1 fix pack 1 7 Update 65 Build 19

Go back to top

Rate this page:

(0 users)Average rating

Document information


More support for:

Runtimes for Java Technology
Java SDK

Software version:

7.1

Operating system(s):

AIX, Linux, Linux zSeries, Windows, i5/OS, z/OS

Software edition:

Java SE

Reference #:

1639279

Modified date:

2014-08-01

Translate my page

Machine Translation

Content navigation