Friday May 17, 2013

New Java SE Version Numbering Scheme!

The releases with new functionalities and non-security fixes also called Limited Update Releases will be numbered in multiples of 20. The Critical Patch Updates (CPUs) will be calculated by adding multiples of five to the prior Limited Update and when needed adding one to keep the resulting number odd.

As an example: The next Limited Update for JDK 7 will be numbered 7u40, and the next 3 CPUs after that will be numbered 7u45, 7u51, and 7u55. The next release will be a Limited Update 7u60, followed by CPUs 7u65, 7u71, and 7u75.

This new version system will apply to JDK 5, JDK 6 and JDK 7 which are available on OTN Java SE Download page and

The change will: 
  • assign a fix/enhancement to a specific release in the bug systems. 
  • prevent the existing code from breaking. the versions will follow the format 7u44 and will not allow 7u44-2 for example.
  • leave “space” between planned releases for any potential unplanned ones. 

Tuesday Dec 11, 2012

Java SE Updates

Duke's helpers from around the world have been busy making Java just right for all good developers. Here are the updates: 

Java SE 7 Update 10  NOTE: This link was changed to a more user-friendly download page on
This releases provides key security features and bug fixes. Oracle strongly recommends that all Java SE 7 users upgrade to this release. JavaFX 2.2.4 is now bundled with the JDK on Windows, Mac and Linux x86/x64.
Learn more Download

This release provides security features and bug fixes. Oracle strongly recommends that all Java SE 6 users upgrade to this release (or to Java SE 7 update 10).

This releases provides the security features and bug fixes from Java SE 7 Update 10.

This releases provides the security features and bug fixes from Java SE 6 Update 38.

NOTE: The end of public updates for Java SE 6 will occur in February 2013. See "The End of Public Updates for Java SE 6" and the Java SE Support Roadmap for more information.

Monday Dec 03, 2012

End of Public Updates for Java SE 6

It's important for developers and systems administrators to either make the transition over to Java SE 7 or to work with Oracle to get updates via the Java SE Support program.

Have you updated to Java SE 7? Along with great features (Fork/Join, NIO, Project Coin), Java SE 7 is being updated and patched regularly. Java SE 7 has been out for over a year and is ready to download

The last publicly available release of Oracle JDK 6 is to be released in February, 2013. This means that after 19 February 2013, all new security updates, patches and fixes for Java SE 6 and Java SE 5 will only be available through My Oracle Support and will thus require a commercial license with Oracle.   

In the event you are not ready to migrate to Java SE 7, Oracle offers:

Java SE Support for continued access to critical bug fixes and security fixes as well as general maintenance for JDK 6. Additionally, Java SE Advanced and Suite offers superior diagnostics and manageability tools that minimize the costs of deployment, monitoring and maintenance of Java-based IT environments.

The Java SE Support Roadmap reflects an updated timeline for the End of Public Updates for JDK 6. The End of Public Updates date has been extended from November 2012 to February 2013, to allow some more time for the transition to JDK 7. Older releases of Java SE 6 will still be available on the Java SE archive, but will require a commercial license with Oracle for any new security updates, patches and fixes. 

Th End of Public Updates for Java SE 6 will not impact the usage, availability, patching of Java SE 6 used for Fusion Middleware 11g and 12c. The support schedule for Java SE used for and in Fusion Middleware is not impacted by this announcement.

For More Information

Visit the Java SE page on

Thursday Apr 26, 2012

Five Java Update Releases

Today, the Oracle Java teams have delivered update releases for Java SE, Java FX and Java SE for Embedded.

Java SE

Java SE 7 Update 4

  • This is the first time Oracle is delivering both the JDK and JavaFX SDK for Mac OS X; the JDK (which will include the JavaFX SDK) is available for download from the Oracle Technology Network Download page.
  • Oracle has continued to work on merging JRockit and HotSpot JVMs to leverage the best features in each.
  • Java SE 7 Update 4 features includes the next-generation Garbage Collection algorithm Garbage First (G1).
  • New JVM (Java HotSpot Virtual Machine, version 23) features JRockit JVM feature convergence. Some of the value-add features of the JRockit JVM are re-implemented in the HotSpot JVM.
  • Java SE 7 Update 4 is the first consumer release of the Java 7 JRE that will be made available as the default version on Follow Henrik Stahl's blog for the latest information.

Java SE 6 Update 32

Java SE 6u32 contains Olson time zone data version 2011l and bug fixes. For more information, see the Java SE 6 Update 32 Release NotesDownload.

Java FX

The JavaFX 2.1 release includes the JavaFX Software Development Kit (SDK) for the Windows and Mac OS X platforms. The JavaFX SDK provides the tools and technologies for developing JavaFX applications with these new features:
  • Playback support for digital media stored in the MPEG-4 multimedia container format containing H.264/AVC video and Advanced Audio Coding (AAC) audio.
  • New Webview support for JavaScript to Java method calls, which allows a user to render HTML/JavaScript and let JavaScript (in WebView) make calls to Java APIs to offload specific operations to Java.
  • The JavaFX 2.1 release adds the ability to use Windows-style LCD sub-pixel rendering. All the JavaFX UI controls will be LCD-text enabled by default on Windows, as will WebView, the Webkit-based node for rendering Web content. Applications can also opt-in to use LCD text on the low-level scenegraph text node by a new API.
  • Additional user interface enhancements in JavaFX 2.1 include: controls for combo box, stacked chart and application-wide menu bar.
  • JavaFX Scene Builder 1.0 Early Access - a visual layout tool for the JavaFX platform. The JavaFX Scene Builder enables designing UI screens by simply dragging and positioning objects.

Java SE for Embedded

Java SE for Embedded 7 Update 4 & Java SE for Embedded 6 Update 32

Java Standard Edition (Java SE) for Embedded Devices delivers a secure, optimized runtime environment that is ideal for network-based devices. Both releases includes bug fixes. Download.

Friday Aug 12, 2011

Java 7 Questions & Answers

By Henrik Stahl, Sr. Director, Product Management, Java Platform Group

This blog entry will be used to host commonly asked questions related to Java 7. I have pre-seeded it with a few that have come up since the July 28 release. If you have additional questions, feel free to post as a comment to the blog. I will not respond to them in the comments, but will instead aggregate and update the blog entry. Only questions of general interest to the community will be answered here. Fire away!

Q: Where can I download Java 7?
A: From, where you can find the JDK 7 download page.

Q: When will JRockit be available for Java 7?
A: It won't. As we explained last year we are merging JRockit and HotSpot into one single JVM. JDK 7 contains the first release of this converged JVM, where one of the first steps was to start removing the PermGen concept. Future JDK 7 updates will complete the PermGen removal, as well as add more visible features from JRockit.

Q: Where can I find the source code?

A: The source code for the Java SE 7 Reference Implementation is available from the JDK 7 Project in the OpenJDK Community.

Q: Why isn't Java 7 available on yet?
A: The site is used for end-user downloads. As with previous major versions of Java, JDK 7 is first made available to developers so that they can ensure that their Java programs work with the new JRE version before it gets rolled out to millions of end-users.

Q: Where can I find API documentation?
A: Javadocs are available here.

Q: What is the status of the port of Java 7 to the Mac?
A: Feature development is still going on in the OpenJDK Mac OS X Port 7 Project. You can see the detailed status here. Once that Project has made sufficient progress - say a couple of months from now or so - we plan to build and make a developer preview available from the main JDK download site. We will then work with Apple and others in the Mac OS X Port Project to finalize remaining feature work such as installers and plugin/webstart, and then go through the usual steps of one or more beta releases and/or release candidates before we get to GA. If you are anxious to get started, there are a number of third parties that provide binary builds from the OpenJDK code. Just use your favorite search engine and you'll find several.

Q: I have read about issues with Apache Lucene running on JDK 7, what is that about?
A: The Lucene project has reported that running Lucene triggers a JIT bug that causes a JVM crash. It can be worked around by disabling the broken optimizations with command line options, see the bug reports for details. The three bugs that Lucene reported have been fixed in the OpenJDK code, in addition to a fourth bug impacting Lucene that Oracle found (7070134, 7068051, 7044738, 7077439), and are included in current builds of JDK 7 Update 1 (and will remain included unless the fixes cause regressions). For more information on how Oracle prioritizes and works with external bug reports see this blog by Dalibor Topic. And while I'm at it - many thanks to all those of you who have tested JDK 7 and reported issues!

Q: I read the JDK 7 license. It mentions something about Commercial Features, what does that mean?
A: Sun had a habit of creating a new license for every version of Java they released (including every update release). While the modifications were minor, it still meant that you had to call in the lawyers every time to verify that any changes from the previous ones were still acceptable to you. Our goal is to minimize the number of licenses we use, ideally getting it down to only one. When we made JRockit free we modified the Binary Code License to make it cover all versions of Java, as well as JRockit. This was announced in one of my previous blog posts. The "Commercial Features" clause is there to allow us to port over value-add features from JRockit to the converged Hotspot/JRockit JVM starting with JDK 7. Full details on what features are non-free can be found in the product documentation. In the standard JDK 7 GA binaries, there are no commercial features so there is no risk that you use them by mistake. As we move such features to JDK 7 in a future update, our plan is to require an explicit flag to enable them. Note that these features are only restricted "for any commercial or production purpose" so individual developers need not worry. For full information, read the license text itself.

Originally published on Henrik's blog.

Tuesday Aug 09, 2011

A Bug's Life: Java 7 Updates

by Dalibor Topic,  Java F/OSS Ambassador, Oracle Java Platform Group

The JDK 7 Updates Project in OpenJDK is now up and running. We've spent some time in the past couple of weeks discussing processes, finalized them, and started accepting changes destined for JDK 7 Update releases.

Changes going into a JDK 7 Update are typically bug fixes, coming to JDK 7 Updates through JDK 8. Bugs get reported through several channels - for example through Oracle's QA engineers running tests on early access builds, an OpenJDK developer working on some piece of code, or through the web bug report form.

When a Java developer or end user reports a bug through the web bug report form, a process kicks off. All bugs coming in through the web bug report form start with the initial priority 4, i.e. 'Low'. Priorities can go from 5, i.e. 'Very Low' all the way up to 1, i.e. 'Very High'. When you're starting to hack on OpenJDK, it can be easier to do so by picking out a couple of P4, or P5 bugs from the bug database in order to learn how the processes work with some success before you go on to tackle harder tasks.

There is a WebBugs team at Oracle that reviews the incoming bug reports, in order to weed out duplicates, or misfiled issues, and if necessary request additional information from the submitter. Not all bugs are created equal, so the low priority automatically assigned by the system to the incoming bugs sometimes needs to be adjusted, as well.

When adjusting the priority of a bug, we look at three aspects: Impact, Likelihood & Workaround. Impact is determined by taking a look at how severe an issue is: A VM crash would have a high impact, for example. On the other hand, the likelihood of the crash occurring could be very low. And finally, the existence of a workaround, in particular an easily applicable one, would also impact the priority of the bug. A high impact bug that strikes often and has no workaround would accordingly get a higher priority then a 'benign' bug that occurs rarely and has an easily applicable workaround.

The priority is not set in stone - as OpenJDK developers start investigating an issue in order to produce a fix for JDK 8, new information regarding impact, likelihood or workaround can emerge, resulting in an update of the bug's priority. For example, if a bug turns out to have a much higher likelihood to occur then initially thought, that could be a good reason to raise its priority. On the other hand, if e.g. an easily applicable workaround is found, that could be a good reason to lower it.

Another important dimension of a bug, along with its priority, is its state. For bugs in process of being addressed, there are three important states to be familiar with: 'Fix In Progress', 'Fix Available', and 'Fix Delivered'. The first one (obviously) means that a fix is in progress. 'Fix Available' means that a fix has been delivered into an OpenJDK Mercurial forest. Typically, the bug's evaluation in the bug database is updated to include a URL to the commit in OpenJDK, as well - look for the line starting with "" if you want to see the source code for a specific bug fix. The fix then progresses through a sequence of integrations into the respective Project's master. For JDK 7 Updates that sequence is fairly short, since we only have one integration forest (jdk7u-dev) in OpenJDK. Finally, once a fix appears in a build, its state is set to 'Fix Delivered'.

With these two bits of information, you can follow along your (and other people's) issues progress in JDK 8 and JDK 7 Updates. For some code, like HotSpot fixes, the path can be a bit longer, since the HotSpot team uses the HotSpot Express model to develop stable versions of HotSpot into multiple JDK releases, so the fix first needs to make it into a HotSpot build, before it can get into JDK 7 Updates through a bulk change. As fixes progress through integration stages, our testing machinery is hammering on them to make sure they work well, work well together, and hold up under pressure.

So, thanks for testing JDK 7, and letting us know about the bugs that bug you. With JDK 7 Updates now up and running, you can help us weed regressions out by testing early access builds, and of course by following along on the jdk7u-dev mailing list as fixes are proposed, reviewed and approved for JDK 7 Updates, and reporting issues you find to our bug tracker.

On a side note, we're working on updating our bug tracking infrastructure used in OpenJDK, which should further increase the transparency of both JDK 8 and JDK 7 Update development in the future.

(originally published on Dalibor Topic's blog.)


Insider News from the Java Team at Oracle!



« June 2016