7. That this bug is specific to HotSpot Server. It doesn't exist in HotSpot Client (which doesn't even have the loop optimization that is buggy...). So the JRE, which only includes the Client VM, is safe. All desktop apps (ok... dev apps like Eclipse/NB etc.) are safe. The JDK doesn't have auto-update, people running server apps always need to explicitly and manually install a new JDK typically, and (unless they are insane) they don't adopt a major new JVM without at least a modicum amount of testing and evaluation; so in this case just add - XX:-UseLoopPredicate - not doom&gloom even for servers.
A+ Osvaldo On Jul 30, 8:26 am, Fernando Cassia <[email protected]> wrote: > On Sat, Jul 30, 2011 at 08:34, Fabrizio Giudici > > <[email protected]> wrote: > > 1. Were these loop-breaking optimizations introduced by default only in > > 7.0GA - so they weren't in betas? > > 2. If answer#1 is "no", did they try Lucene with betas? > > I was able to find some more info and it turns out that: > > 1. that Oracle learned about it 5 days before GA release, and promised > a fix for the first JDK7 security update > > 2. that Java 6 users are also affected, if they enable > -XX:+OptimizeStringConcat or > -XX:+AggressiveOptshttp://pages.citebite.com/d9y2u1i5bnjm > > 3. That this doom and gloom bug (according to tweets) actually affects > very specific conditions, and there is a work-around. In the words of > the poster: > > -----> These problems were detected only 5 days before the official Java 7 > release, so Oracle had no time to fix those bugs, affecting also many more > > applications. In response to our questions, they proposed to include the > > fixes into service release u2 (eventually into service release u1, see > > [http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2011-July...]). > > This means you cannot use Lucene/Solr with Java 7 releases before Update 2! > > If you do, please don't open bug reports, it is not the committers' fault! > > At least disable loop optimizations using the -XX:-UseLoopPredicate JVM > > options > > ----- > > 4. As usual h-online has some of the best, in-depth reporting when it > comes to Java, without apocalypse headlines that I´m sure will appear > in other sites like TheReg... > > Java 7 paralyses Lucene and > Solrhttp://www.h-online.com/open/news/item/Java-7-paralyses-Lucene-and-So... > > 5. "Don´t use Java 7 for *anything*" seems to me like just bad faith, > specially given the availability of a work-around (point #3 above). > > 6. I wonder if, in situations like this, it wouldn´t be possible just > to issue a 7.01 that runs with the work-around parameter ( > -XX:-UseLoopPredicate ) all the time, whether present and passed by > the user or not. > > FC -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
