No Oracle fixed the problem in 7u1, see http://blog.thetaphi.de/2011/10/java-7-update-1-released-does-it-fix.html If you use Java 7 GA then your index is corru(m)pt in milliseconds :-)
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Jack Krupansky [mailto:[email protected]] > Sent: Thursday, September 20, 2012 6:26 PM > To: [email protected] > Subject: Re: Is it safe to upgrade to Oracle Java 7u7 for Lucene/Solr > development and use? > > Thanks, but I was under the impression that there was a release of 1.7 that > did > not work properly with Lucene. Or, was there a workaround in a subsequent > release of Lucene so that Lucene/Solr (3.6, 3.6.1, 4.0, 5.0) now works with > even > that early Java 7 release that failed with earlier releases of Lucene/Solr? > > > -- Jack Krupansky > -----Original Message----- > From: Robert Muir > Sent: Thursday, September 20, 2012 11:45 AM > To: [email protected] > Subject: Re: Is it safe to upgrade to Oracle Java 7u7 for Lucene/Solr > development and use? > > BUILD.txt: > > Lucene Build Instructions > > Basic steps: > 0) Install JDK 1.6 (or greater) > > On Thu, Sep 20, 2012 at 11:40 AM, Jack Krupansky > <[email protected]> wrote: > > Okay, that was the one place I hadn’t looked. Thanks. Still, it seems > > to me that a release should clearly state what it requires, and there > > is no mention in the 4.0 text files what Java versions are supported, > > other than the ambiguous references I mentioned. I mean, if someone is > > starting out with 4.0, why should they have to read the release notes > > for 3.6?? > > > > -- Jack Krupansky > > > > From: Uwe Schindler > > Sent: Thursday, September 20, 2012 10:52 AM > > To: [email protected] > > Subject: RE: Is it safe to upgrade to Oracle Java 7u7 for Lucene/Solr > > development and use? > > > > > > We already stated that in Lucene 3.5/3.6 release note! It’s fine since > > Java 7u1. There are no news in Lucene 4.0 > > > > > > > > ----- > > > > Uwe Schindler > > > > H.-H.-Meier-Allee 63, D-28213 Bremen > > > > http://www.thetaphi.de > > > > eMail: [email protected] > > > > > > > > From: Jack Krupansky [mailto:[email protected]] > > Sent: Thursday, September 20, 2012 4:49 PM > > To: Lucene/Solr Dev > > Subject: Is it safe to upgrade to Oracle Java 7u7 for Lucene/Solr > > development and use? > > > > > > > > The Oracle Java Update tool on my Windows PC is pretty insistent that it > > wants to update my machine to Java 7u7 and REMOVE Java 6. Is it safe to > > use > > Java 7u7 for both Lucene Solr development and running Solr yet? My > > presumption has been that Lucene/Solr still “requires” Java 6. > > > > > > > > The 4.0 Solr README.txt says to use the Java 6 JDK, but then adds “verify > > > > that the Java version is 1.6 or later ”, implying that a later release > > would > > be okay. Given that Java 7 will be the “current” release, the README > > should > > make some specific statement regarding Java 7. > > > > > > > > And maybe the top-level README.txt should have a Java version statement – > > unless both 7 and 6 are fine – although there is a minimum update level > > that > > works for 7 and Lucene, right? In any case, clear guidance should be > > provided. > > > > > > > > The Solr 4.0 CHANGES.txt does say “You > > > > need a Java 1.6 VM or later installed”, suggesting that Java 7 is fine. No > > mention of Java version requirement in the Lucene CHANGES.txt. > > > > > > > > I may just manually install 7u7 and not use it to avoid the update notice > > until Lucene/Solr “upgrades” to Java 7, but I suspect a fair number of > > people will simply take the update and say goodbye to Java 6. > > > > > > -- Jack Krupansky > > > > -- > lucidworks.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
