Update Release Notes

Update Release Notes Index

Java™ SE 6 Update 29

The full internal version number for this update release is 1.6.0_29-b11 (where "b" means "build"). The external version number is 6u29.

Olson Data 2011g

Java SE 6u29 contains Olson time zone data version 2011g. For more information, refer to Timezone Data Versions in the JRE Software .

Security Baselines

The security baselines for the Java SE platform at the time of the release of Java SE 6u29 are specified in the following table:

JRE Family Version Java for Business
Security Baseline
6 1.6.0_29
5.0 1.5.0_32
1.4.2 1.4.2_34

On October 30, 2008, Java SE 1.4.2 reached its end of service life with the release of 1.4.2_19. Java SE 5.0 reached its end of service life on November 3, 2009, with the release of 5.0u22. Future revisions of Java SE 1.4.2 (1.4.2_20 and above) and Java SE 5.0 (5.0u23 and above) are available to Java for Business subscribers.

For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer .

Skipped Version Number

Release Java SE 6u29 follows release Java SE 6u27. There is no publicly available Java SE 6u28 release. Oracle used release version 6u28 for an internal build, which was not necessary once the fixes delivered on Java SE 6u29 were released.

Blacklist Entries

This update release includes the following new entries to the Blacklist:

Note: For more information, see the Blacklist Jar Feature section in the Java SE 6u14 Release Notes.

RMI Registry Issue

A bug in the rmiregistry command included in this release may cause unintended exceptions to be thrown when an RMI server attempts to bind an exported object which includes codebase annotations using the "file:" URL scheme. The RMI servers most likely to be effected are those which are invoked only by RMI clients executing on the same host as the server.

RMI annotates codebase information as part of the serialized state of a remote object reference to assist RMI clients in loading the required classes and interfaces associated with the object at runtime. Exported objects which are looked up in the RMI registry and invoked by RMI clients running on hosts other than the server are usually annotated with codebase URL schemes, such as "http:" or "ftp:" and these should continue to work correctly.

As a workaround, RMI servers can set the java.rmi.server.codebase property to use codebase URLs other than the "file:" scheme for the objects they export.

Bug Fixes

This release contains fixes for security vulnerabilities. For more information, please see Oracle Java SE Critical Patch Update advisory.

JIT and Loop Bugs

Three bugs reported by various parties, including Apache Lucene developers, have been fixed in JDK 6 Update 29, in addition to a fourth related bug found by Oracle (7070134, 7068051, 7044738, 7077439).

Other Bug Fixes


Bug ID Category Sub-Category Synopsis
7041200  java classes_net java.net.InterfaceAddress's equals method may throw NPE
6942989  java classes_util_logging Memory leak of java.lang.ref.WeakReference objects
7037336  java_deployment download Downloading of resources with redirect URL should remember final URL
7038810  java_plugin misc Regression: JNLP applet with file protocol failed to download
7032687  java_plugin plugin Dragged-out applet can be closed when close browser