Java 7 GA 今天發(fā)布了，但是如Uwe Schindler 所述，HotSpot Loop optimizations存在一些非?？膳碌哪J(rèn)啟用的bug。***的情況下，這些bug會導(dǎo)致JVM崩潰，最壞的情況下，會導(dǎo)致loops的不正確的執(zhí)行。

十載的潼關(guān)網(wǎng)站建設(shè)經(jīng)驗，針對設(shè)計、前端、開發(fā)、售后、文案、推廣等六對一服務(wù)，響應(yīng)快，48小時及時工作處理。全網(wǎng)營銷推廣的優(yōu)勢是能夠根據(jù)用戶設(shè)備顯示端的尺寸不同，自動調(diào)整潼關(guān)建站的顯示方式，使網(wǎng)站能夠適用不同顯示終端，在瀏覽器中調(diào)整網(wǎng)站的寬度，無論在任何一種瀏覽器上瀏覽網(wǎng)站，都能展現(xiàn)優(yōu)雅布局與設(shè)計，從而大程度地提升瀏覽體驗。創(chuàng)新互聯(lián)從事“潼關(guān)網(wǎng)站設(shè)計”,“潼關(guān)網(wǎng)站推廣”以來，每個客戶項目都認(rèn)真落實執(zhí)行。

除非，除非在你的Java代碼里面不用任何的loops。

附 Uwe Schindler 的郵件：

From: Uwe Schindler

Date: Thu, 28 Jul 2011 23:13:36 +0200

Subject: [WARNING] Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7

Hello Apache Lucene & Apache Solr users,

Hello users of other Java-based Apache projects,

Oracle released Java 7 today. Unfortunately it contains hotspot compiler

optimizations, which miscompile some loops. This can affect code of several

Apache projects. Sometimes JVMs only crash, but in several cases, results

calculated can be incorrect, leading to bugs in applications (see Hotspot

bugs 7070134 [1], 7044738 [2], 7068051 [3]).

Apache Lucene Core and Apache Solr are two Apache projects, which are

affected by these bugs, namely all versions released until today. Solr users

with the default configuration will have Java crashing with SIGSEGV as soon

as they start to index documents, as one affected part is the well-known

Porter stemmer (see LUCENE-3335 [4]). Other loops in Lucene may be

miscompiled, too, leading to index corruption (especially on Lucene trunk

with pulsing codec; other loops may be affected, too - LUCENE-3346 [5]).

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 [6]).

This means you cannot use Apache 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 option to not risk index corruptions.

Please note: Also Java 6 users are affected, if they use one of those JVM

options, which are not enabled by default: -XX:+OptimizeStringConcat or

-XX:+AggressiveOpts

It is strongly recommended not to use any hotspot optimization switches in

any Java version without extensive testing!

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

JRE_VERSION_MIGRATION.txt in your distribution package!

On behalf of the Lucene project,

Uwe

[1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134

[2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7044738

[3] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068051

[4] https://issues.apache.org/jira/browse/LUCENE-3335

[5] https://issues.apache.org/jira/browse/LUCENE-3346

[6] http://s.apache.org/StQ

原文：http://www.oschina.net/news/20170/java7-bug

當(dāng)前文章：小心bug！慎用Java7
文章源于：http://uogjgqi.cn/article/cdhoiis.html