A severe optimization bug in Java 7 is affecting the Apache Lucene project which is heavily used by Hibernate Search. If you are using any version of Hibernate Search and contemplate using Java 7, please read.
In one line: do not use or you might get index corruption and VM crashes.
Some details
a loop optimization bug is present in Java 7
it can lead to either crash or index corruption when running Hibernate Search
Oracle is aware of the problem and is working for a fix for update 2 (and maybe update 1)
this bug also affect Java 6 VMs assuming you use some VM optimization options (-XX:+OptimizeStringConcat or
-XX:+AggressiveOpts)
A severe optimization bug in Java 7 is affecting the Apache Lucene project
which is heavily used by Hibernate Search. If you are using any version of
Hibernate Search and contemplate using Java 7, please read.
In one line: do not use or you might get index corruption and VM crashes.
Some details
a loop optimization bug is present in Java 7
it can lead to either crash or index corruption when running Hibernate
Search
Oracle is aware of the problem and is working for a fix for update 2 (and
maybe update 1)
this bug also affect Java 6 VMs assuming you use some VM optimization
options (-XX:+OptimizeStringConcat or
-XX:+AggressiveOpts)
Hey Shay,
Does it mean that ES versions based on Lucene 3.3 does not suffer no matter
which JVM version they are running on?
Rgds,
Lukas
Dne 29.7.2011 10:12 "Shay Banon" kimchy@gmail.com napsal(a):
Heya,
Yea, I was just writing this email to the mailing list as well... . Note,
the index corruption only affects Lucene trunk.
-shay.banon
On Fri, Jul 29, 2011 at 11:09 AM, David Pilato david@pilato.fr wrote:
A severe optimization bug in Java 7 is affecting the Apache Lucene
project
which is heavily used by Hibernate Search. If you are using any version
of
Hibernate Search and contemplate using Java 7, please read.
In one line: do not use or you might get index corruption and VM crashes.
Some details
a loop optimization bug is present in Java 7
it can lead to either crash or index corruption when running Hibernate
Search
Oracle is aware of the problem and is working for a fix for update 2
(and
maybe update 1)
this bug also affect Java 6 VMs assuming you use some VM optimization
options (-XX:+OptimizeStringConcat or
-XX:+AggressiveOpts)
Hey Shay,
Does it mean that ES versions based on Lucene 3.3 does not suffer no matter
which JVM version they are running on?
Rgds,
Lukas
Dne 29.7.2011 10:12 "Shay Banon" kimchy@gmail.com napsal(a):
Heya,
Yea, I was just writing this email to the mailing list as well... . Note,
the index corruption only affects Lucene trunk.
-shay.banon
On Fri, Jul 29, 2011 at 11:09 AM, David Pilato david@pilato.fr wrote:
A severe optimization bug in Java 7 is affecting the Apache Lucene
project
which is heavily used by Hibernate Search. If you are using any version
of
Hibernate Search and contemplate using Java 7, please read.
In one line: do not use or you might get index corruption and VM
crashes.
Some details
a loop optimization bug is present in Java 7
it can lead to either crash or index corruption when running Hibernate
Search
Oracle is aware of the problem and is working for a fix for update 2
(and
maybe update 1)
this bug also affect Java 6 VMs assuming you use some VM optimization
options (-XX:+OptimizeStringConcat or
-XX:+AggressiveOpts)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
