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 7u72) will expire with the release of the next critical patch update scheduled for January 20, 2015.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u72) on February 20, 2015. 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.
JavaFX Release Notes
This JDK release includes JavaFX version 2.2.72.
Selecting a Suitable JDK 7 Release
In this release, both JDK 7u71 and JDK 7u72 products are available. JDK 7u71 (CPU) contains vulnerability fixes and JDK 7u72 (PSU) contains all the fixes from 7u71 plus additional non-critical stability fixes.
Use JDK 7u71 release unless you need one of the additional fixes found on the JDK 7u72 release. For mission critical applications you should test with the PSU release regardless of whether you chose to use the CPU or the PSU as the fixes on the PSU will be included in the next CPU.
Instructions to disable SSL v3.0 in Oracle JDK and JRE
Unsafe Server Certificate Change in SSL/TLS Renegotiations Not Allowed.
Starting with JDK 7u71, unsafe server certificate change in SSL/TLS renegotiations is not allowed by default. Server certificate change in an SSL/TLS renegotiation may be unsafe and should be restricted:
if endpoint identification is not enabled in an SSL/TLS handshaking; and
if the previous handshake is a session-resumption abbreviated initial handshake; and
the identities represented by both certificates (in previous handshake and this handshake) cannot be regraded as the same.
If unsafe server certificate change is really required, please set the system property, jdk.tls.allowUnsafeServerCertChange, to "true" before JSSE is initialized. Note that this would re-establish the unsafe server certificate change issue.
Change in javax.smartcardio.Card.disconnect(boolean reset) method behavior
Prior to the JDK 8u20 and JDK 7u72 releases, the javax.smartcardio.Card.disconnect(boolean reset) method had inverted logic for the 'reset' boolean value passed to it. The card was reset upon a disconnect if false was passed to it and vice versa. Starting with JDK 7u72 and JDK 8u20, the correct behavior as per API documentation has been implemented.
In order to provide backwards compatibility to users who rely on the old behavior, a new system property has been introduced. The following command-line option can be used to enforce the old broken behavior:
This property is set by default for 7u72 and later JDK 7 update releases. By default, no behavioral change will be noticed in this area for JDK 7 update releases.
Also the following command-line option can be used to enforce the new correct behavior:
This is default for 8u20 and later JDK 8 update releases. In future Java releases, the property will be ignored/disabled and default disconnect method behavior will be as specified by API.