IBM SDK, Java Technology Edition, Version 7 Service Refresh 5 general availability.
Service refresh 5 is now available for download on all platforms and contains the following changes:
- Improvements to Java core information
- File descriptors are now closed immediately
- LiveConnect is now disabled in certain circumstances
- Behavior change to java.lang.logging.Logger
- Change in behavior when using XSLT extension elements or functions
- Updated Health Center agent
For any late breaking news or supplementary information that is not included in the Information Center , see IBM SDK, Java Technology Edition, Version 7: Current news
For any security fixes provided in this service refresh, see the list of Security alerts.
For a list of the IBM fixes included, see IBM SDK, Java Technology Edition, Version 7 fixes.
Visit developerWorks: IBM developer kits to download the service refresh.
Improvements to Java core information
A new line is now recorded to show the ID of the operating system process that produced the javadump file.
File descriptors are now closed immediately
There is a change to the default behaviour of the close() method of the FileInputStream, FileOutputStream, and RandomAccessFile classes. In previous releases, the default behavior was to close the file descriptor only when all the streams that were using it were also closed. The new default behavior is to close the file descriptor regardless of any other streams that might still be using it. You can revert to the previous default behavior by using a system property, however this property will be removed in future releases. For more information, see -Dcom.ibm.streamsCloseFDWithStream.
LiveConnect support is now disabled in certain circumstances
- The security level on the Security tab of the IBM Control Panel for Java is set to Very High.
- The security level on the Security tab of the IBM Control Panel for Java is set to High (default) and the runtime environment has expired. The runtime environment automatically expires after 6 months. To ensure that your runtime environment remains secure, install the latest release.
Note: The security level setting is present only in very recent releases.
Behavior change to java.lang.logging.Logger
To enhance security, java.lang.logging.Logger no longer walks the stack to search for resource bundles. Instead, the resource bundles are located by using the caller 's class loader. If your application depends upon stack-walking to locate resource bundles, this behavior change might affect your application. To work around this problem, a system property is available in this release to revert to the earlier behavior. To set this property on the command line specify: -Djdk.logging.allowStackWalkSearch=true.
Unexpected XSLT error on extension elements or extension functions when Java security is enabled
Any attempt to use extension elements or extension functions when Java security is enabled, results in a javax.xml.transform.TransformerException error during XSLT processing. This change in behavior is introduced to enhance security. For more information, see Unexpected XSLT error on extension elements or extension functions when Java security is enabled.
Health Center agent
This release contains a later level of the IBM Monitoring and Diagnostic Tool for Java Health Center agent. To learn about the function included with this agent, see http://publib.boulder.ibm.com/infocenter/hctool/v1r0/topic/com.ibm.java.diagnostics.healthcenter.doc/topics/platforms.html.