Java 7 screwup

[John Yeary]

As with any major release, there are bound to be bugs. However, the OpenJDK
project announced the release and freeze on the code for what would become
JDK 7. No one reported any major issues prior to launch. The folks on Apache
Lucene/Solr projects could have tested in advance of release and found these
issues. This may have prevented the on-time release.

I am not blaming the Apache folks, or Oracle. As with any new software, you
need to test it. I have not been affected by the bug(s) reported, and can
happily continue on my computing way. The workarounds have been released,
use them until a fix is out, or alternatively wait and use JDK 6. As noted
in the article, these JVM options are disabled in 6 and the bug was present.


No one noticed this previously so I surmise that it is a mountain-mole hill
issue.

John

On Fri, Aug 5, 2011 at 5:00 AM, Mark Derricutt <mark at talios.com> wrote:

> That would be the loop optimization bug which the Apache Lucene/Solr
> project discovered shortly before the release.
>
> For the *REAL* story behind the bug in question, and the ensuing press
> reaction:
>
> http://blog.thetaphi.de/2011/07/real-story-behind-java-7-ga-bugs.html
>
> Personally, I'm wondering why the release didn't get pulled and a new
> release didn't get rolled disabling the optimizations.  ( I'm also actually
> really curious, what would it have taken for Oracle to pull the release if
> not something potentially as bad as this? ).
>
> Mark
>
>
>
> On 5/08/2011, at 7:14 PM, Kelly O'Hair wrote:
>
> > What is this email about?
> > What's wrong with Java 7?
>
>


-- 
John Yeary
--
http://javaevangelist.blogspot.com
http://www.johnyeary.com
*@jyeary*

"Far better it is to dare mighty things, to win glorious triumphs, even
though checkered by failure, than to take rank with those poor spirits who
neither enjoy much nor suffer much, because they live in the gray twilight
that knows not victory nor defeat."
-- Theodore Roosevelt