Java 6 End of Public Updates extended to February 2013

Earlier this year I announced that the EOL for Oracle JDK 6 had been extended from July 2012 to November 2012. JDK 6 was the default JDK for over 5 years, and so it seems fair that it have a longer publicly available support time-frame than past major releases.

After further consultation and consideration, the Oracle JDK 6 End of Public Updates will be extended through February, 2013. This means that the last publicly available release of Oracle JDK 6 is to be released in February, 2013. After the End of Public Updates for JDK 6, if you have a valid support contract for an Oracle product that requires JDK 6, or an Oracle Java SE Support contract, there will still be additional support versions of JDK 6 available from My Oracle Support. Previously available versions of JDK 6 will remain available to the public through the Java Archive for debugging and testing purposes but Oracle no longer recommends using those in production.

It's important to highlight that, as we establish a steady two year cadence for major releases, End of Public Update events for major versions will become more frequent. As a reminder, moving forward, Oracle will stop providing public updates of a major JDK version once all of the following criteria have been met:

  • Three years after the GA of a major release
  • One year after the GA of a subsequent major release
  • Six months after a subsequent major release has been established as the default JRE for end-user desktops on

For more information see the FAQ on OTN.


I have a shirt from Oracle that has Java 7 Moving Java Forward on it. You keep pushing the EOL back, and it is causing companies to delay making the changes necessary to keep Java moving forward.

The JUG leaders list had a discussion about an article that the MS FUD council published about security issues in Java. The discussion focused on two main points: keeping JRE/JVM up to date, and a more fluid update mechanism to keep it that way. Lack of forward movement will go a long way in helping to keep the FUD coming.

Oracle has done a lot of work to advance Java. Make that the focal point by driving adoption of the community (OpenJDK), and Oracle's good work.

Do you think that a change of two months is going to make a real difference? Those who are short sighted will just wait for the next extension, or fail horribly when it does not arrive.

I think it is important to be consistent in these matters, but now that beast has been let loose; it cannot be caged.

Please don't falter and stay the course. Let Jan 2013 be the last EOL, and lets: Move Java Forward.

Posted by guest on August 09, 2012 at 05:28 AM PDT #

Hi John! Couldn't agree more on the desire to move to Java 7 as soon as possible. However, due to the long delay between Java 6 and 7, a lot of organizations small and large have not been prepared. We have been made aware of some major issues that would be caused if we rushed autoupdate from 6 to 7 on end-user desktops (a prerequisite to the End of Public Updates milestone). The extra months we are adding will enable these organizations to do an orderly update of their code and processes. We have no plans for any additional extensions, and will work hard to keep broadcasting the message that it's time to move to 7. Regards -- Henrik

Posted by Henrik on August 09, 2012 at 07:30 AM PDT #


The companies also usually wait for a certain level of maturity on all platforms where a particular level of Java is available.

So, the delay is rather welcome and allows for better preparedness.

The Java User.

Posted by Java User on August 09, 2012 at 10:35 AM PDT #


This will allow a graceful transition of all Java 6 applications to Java 7, and give me time to learn Java 7 better before I have to use it intensively.

Posted by guest on August 13, 2012 at 07:40 AM PDT #

Since your updates are only 3x a year and you left a gaping hole in security that forces some users to completely shut down java may want to re-think drop dead dates for older versions and the inability for users and administrators to fall back to older (less buggy) versions. At least Microsoft can patch its foibles weekly.

Posted by cuba_pete on August 28, 2012 at 07:28 AM PDT #

Post a Comment:
Comments are closed for this entry.

Henrik Stahl is VP of Product Management in the Java Platform Group at Oracle, and is responsible for product strategy for Java ME and SE.


« July 2016