拈花微笑 » oracle

Don’t Use Java 7, For Anything [zz]

Jay — Wed, 10 Aug 2011 08:08:36 +0000

From here. Shit happens, Oracle wanna risk the fame of Java?!

Java 7 GA was released today, but as noted by Uwe Schindler, there are some very frightening bugs in HotSpot Loop optimizations that are enabled by default. In the best case scenario, these bugs cause the JVM to crash. In the worst case scenario, they cause incorrect execution of loops.

Bottom Line: Don’t use Java 7 for anything (unless maybe you know you don’t have any loops in your java code)

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

原创内容，转载请注明： 转载自拈花微笑

本文链接地址: Don’t Use Java 7, For Anything [zz]

如何在CLI下更新Glassfish

Jay — Fri, 10 Sep 2010 09:22:58 +0000

Glassfish作为由Sun（现在是Oracle）及社区直接维护的开源Java EE应用服务器，其对Java EE 6标准的全面支持、稳定强劲的运行表现和简单全面的配置界面赢得了Java社区的一致好评，并已逐渐成为架设Java Web App的首选

GF从2.0开始引入了update tool，即服务器在线版本更新工具，大大方便了开发人员对服务器的升级。然而，对于只有CLI环境的系统，比如远程SSH，默认的GUI版本的update tool无法运行，只能使用pkg代替。本文将介绍xUnix系统下如何使用pkg更新glassfish，及使用pkg中遇到的问题的解决方法

进入GF/bin目录，执行

./updatetool

./updatetool

GF将会从远程服务器下载updatetool、pkg的相关文件并生成两个脚本：updatetool和pkg。其中updatetool是GUI版本的更新工具，若在图形界面下可直接执行updatetool使用GUI更新GF。pkg是CLI版本。此时直接执行

./pkg

./pkg

可能会得到如下错误：

Traceback (most recent call last):
File "/opt/glassfishv3/pkg/bin/client.py", line 61, in ?
import pkg.actions as actions
File "/opt/glassfishv3/pkg/vendor-packages/pkg/actions/__init__.py", line 59, in ?
globals(), locals(), [modname])
File "/opt/glassfishv3/pkg/vendor-packages/pkg/actions/generic.py", line 45, in ?
import pkg.variant as variant
File "/opt/glassfishv3/pkg/vendor-packages/pkg/variant.py", line 28, in ?
from pkg.misc import EmptyI
File "/opt/glassfishv3/pkg/vendor-packages/pkg/misc.py", line 32, in ?
import OpenSSL.crypto as osc
File "/opt/glassfishv3/pkg/vendor-packages/OpenSSL/__init__.py", line 11, in ?
import rand, crypto, SSL, tsafe
ImportError: /opt/glassfishv3/pkg/vendor-packages/OpenSSL/crypto.so: cannot restore segment prot after reloc: Permission denied

Traceback (most recent call last):
  File "/opt/glassfishv3/pkg/bin/client.py", line 61, in ?
    import pkg.actions as actions
  File "/opt/glassfishv3/pkg/vendor-packages/pkg/actions/__init__.py", line 59, in ?
    globals(), locals(), [modname])
  File "/opt/glassfishv3/pkg/vendor-packages/pkg/actions/generic.py", line 45, in ?
    import pkg.variant as variant
  File "/opt/glassfishv3/pkg/vendor-packages/pkg/variant.py", line 28, in ?
    from pkg.misc import EmptyI
  File "/opt/glassfishv3/pkg/vendor-packages/pkg/misc.py", line 32, in ?
    import OpenSSL.crypto as osc
  File "/opt/glassfishv3/pkg/vendor-packages/OpenSSL/__init__.py", line 11, in ?
    import rand, crypto, SSL, tsafe
ImportError: /opt/glassfishv3/pkg/vendor-packages/OpenSSL/crypto.so: cannot restore segment prot after reloc: Permission denied

根据这篇文章的解决方案，执行

/usr/sbin/setenforce 0

/usr/sbin/setenforce 0

应该就解决了，最后使用如下脚本更新GF

./pkg image-update

./pkg image-update

原创内容，转载请注明： 转载自拈花微笑

本文链接地址: 如何在CLI下更新Glassfish

别了，sun.com

Jay — Fri, 29 Jan 2010 06:46:27 +0000

继前两天欧盟批准oracle对sun的收购案后，今天春男第一时间发现sun.com已被重定向至oracle.com。在里面转了一下，可能是刚刚改版完的原因，sun的product找起来很麻烦，而且都把之前的蓝色色调改成了oracle的红色。看来以后得关注ORCL的股票了。

别了，sun.com

原创内容，转载请注明： 转载自拈花微笑

本文链接地址: 别了，sun.com

Sun 卖了……

Jay — Mon, 20 Apr 2009 14:06:15 +0000

刚刚得到的消息，Oracle收购了Sun，9.5刀一股，一共74亿

这里是Oracle的官方声明
这里是Sun的声明
这里是一篇国外新闻

接下来的时间就看Sun和Oracle的重复部分如何整合（或者舍弃）了

MySQL VS Oracle DB
GlassFish VS WebLogic（不知道之前为什么买了BEA）
JDK VS JRockit
JDeveloper VS Netbeans
红色 VS 蓝色

关注中……

原创内容，转载请注明： 转载自拈花微笑

本文链接地址: Sun 卖了……