The full version string for this update release is 1.7.0_60-b19 (where "b" means "build"). The version number is 7u60.
This update release contains several enhancements and changes including the following:
JDK 7u60 contains IANA time zone data version 2014b. For more information, refer to Timezone Data Versions in the JRE Software.
The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 7u60 are specified in the following table:
|JRE Family Version||JRE Security Baseline (Full Version String)|
For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer.
The JRE expires whenever a new release with security vulnerability fixes becomes available. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. This JRE (version 7u60) will expire with the release of the next critical patch update scheduled for July 15, 2014.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u60) on August 15, 2014. After either condition is met (new release becoming available or expiration date reached), the JRE will provide additional warnings and reminders to users to update to the newer version. For more information, see JRE Expiration Date.
This JDK release includes JavaFX version 2.2.60.
This JDK release includes Java Mission Control(JMC) version 5.3. For more information, see JMC 5.3 Release Notes.
deployment.expiration.check.enabledproperty for first launch
If you have an older version of Java and expiration check is turned off through
deployment.properties file, Java may ignore this property for first launch.
To ensure that expiration check is disabled, use the following Java Web Start command:
javaws -userConfig deployment.expiration.check.enabled false
If this property is changed in the
deployment.properties file, open the Java Control Panel before starting an application to ensure that the native cache is synchronized with the file. For more information, see Deployment Configuration File and Properties.
MaxHeapFreeRatio have been made manageable. This means they can be changed at runtime using the management API in Java. Support for these flags have also been added to the
ParallelGC as part of the adaptive size policy.
For a list of bug fixes included in this release, see JDK 7u60 Bug Fixes page.
The following are some of the notable bug fixes in this release:
Synopsis: Realm.getRealmsList returns realms list in wrong order
Java does not support the [capaths] section in
krb5.conf correctly if there are more then one intermediate realm between the client realm and the server realm.