JDK now comes with an expiration date. Unknown what happens when it expires.
oracle.com
oracle.com
The JRE relies on periodic checks with an Oracle Server to determine if it (the JRE)is still considered up-to-date with all the available security fixes (above the security baseline). In the past, if the JRE was unable to contact the Oracle Server, it continued to behave as though it is still the most recent version with regard to security, for an indefinite period.
To avoid this problem, a secondary mechanism, that does not rely on external communication, has been added to the JDK 7u10. From this release onwards, all JREs will contain a hard-coded expiration date. The expiration date is calculated to end after the scheduled release of the next Critical Patch Update.
This means that JREs that are unable to contact Oracle Servers for an extended period of time, will now start offering additional protection after a reasonable period, and will not continue to behave as if they were still up-to-date with security fixes.
It's known what happens.
Oracle have a policy whereby support for product X.Y.Z.K expires 3 months after X.Y.Z.K+1 is released, or 6 months after X.Y.Z+1 is released. 15 November is 6 months from 15 May, or 3 months from 15 August; do those dates match some other JDK release (actual or planned)?
http://stackoverflow.com/questions/16067829/jre-expiration-d...
LiveConnect calls from JavaScript to Java API are blocked when the Java Control Panel security slider is set to Very High level, or when the slider is at the default High level and the JRE has either expired or is below the security baseline.
It's good and noble enforce the values of a community, but it's far less meaningful to the recipient without that added bit of information.
It makes your fridge smell foul.