lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Created) (JIRA)" <>
Subject [jira] [Created] (LUCENE-3537) Add note about Java 7u1 and 6u29 to Lucene/Solr sites
Date Wed, 26 Oct 2011 10:19:32 GMT
Add note about Java 7u1 and 6u29 to Lucene/Solr sites

                 Key: LUCENE-3537
             Project: Lucene - Java
          Issue Type: Task
          Components: general/website
            Reporter: Uwe Schindler

Oracle confirmed, that the bugs leading to index corruption and SIGSEGV are fixed in Java
7u1 and 6u29. We should post a message to the news sections revising the previous WARNING
(LUCENE-3349). I prepared something, please comment before i commit:

<section><title>26 October 2011 - Java 7u1 fixes index corruption and crash bugs
in Apache Lucene Core and Apache Solr</title>
<p>Oracle released <a href="">Java
7u1</a> on October 19.
According to the release notes and tests done by the Lucene committers, all bugs reported
on July 28 are fixed in this release,
so code using Porter stemmer no longer crashes with <code>SIGSEGV</code>. We were
not able to experience any index corruption anymore,
so it is safe to use Java 7u1 with Lucene Core and Solr.</p>
<p>On the same day, Oracle released <a href="">Java
fixing the same problems occurring with Java 6, if the JVM switches <code>-XX:+AggressiveOpts</code>
or <code>-XX:+OptimizeStringConcat</code> were used. Of course, you should <strong>not</strong>
use experimental JVM options like
<code>-XX:+AggressiveOpts</code> in production environments! We recommend everybody
to upgrade to this latest version 6u29.</p>
<p>In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
version shipped with Java 7 changed and tokenization behaves differently
(e.g. lowercasing). For more information, read <code>JRE_VERSION_MIGRATION.txt</code>
in your distribution package!</p>

I plan to commit this later this afternoon.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message