Our product is used by customers with different appserver/db-setups.
One customer uses Websphere 7, running on the embedded IBM JDK 1.6.0
(windows). We are using embedded elasticsearch in our product.
When starting the server, and trying to create index, the server dies with
some "Type Segmentation error". Same thing happens using Tomcat and the IBM
JDK.
Our previous version of the product, without elasticsearch, are running
fine both on Websphere and Tomcat with IBM JDK. On Oracle JVM, all tested
appserveres are running fine with Elasticsearch.
Our product is used by customers with different appserver/db-setups.
One customer uses Websphere 7, running on the embedded IBM JDK 1.6.0
(windows). We are using embedded elasticsearch in our product.
When starting the server, and trying to create index, the server dies with
some "Type Segmentation error". Same thing happens using Tomcat and the IBM
JDK.
Our previous version of the product, without elasticsearch, are running fine
both on Websphere and Tomcat with IBM JDK. On Oracle JVM, all tested
appserveres are running fine with Elasticsearch.
Possible workarounds I can think of: a brutal disabling of the JIT
compiler. Set -Xint in the JVM arguments in bin/elasticsarch.in.sh. Note,
the performance will be horrible.
A finer JIT disabling is possible by -Xjit:exclude={java-method} but then
you must know in which java method the JIT compiler dies. All in all, you
must be aware that it will be quite frustrating to run ES on an ancient JVM
by JIT patching.
Websphere 7 appeared September, 2008, and predates Elasticsearch and
current Lucene versions. Websphere 8 was released June, 2011. So, beside
upgrading to Java 7, which might not be easy in Websphere 7, an upgrade to
Websphere 8 is another option.
Thank you for replies. We've done successfull testing on Websphere 8.5
Liberty Profile (not without the usual hassle using bigshot appservers :-/
) , so I think this means end-of-life for Websphere 7 support.
Possible workarounds I can think of: a brutal disabling of the JIT
compiler. Set -Xint in the JVM arguments in bin/elasticsarch.in.sh. Note,
the performance will be horrible.
A finer JIT disabling is possible by -Xjit:exclude={java-method} but then
you must know in which java method the JIT compiler dies. All in all, you
must be aware that it will be quite frustrating to run ES on an ancient JVM
by JIT patching.
Websphere 7 appeared September, 2008, and predates Elasticsearch and
current Lucene versions. Websphere 8 was released June, 2011. So, beside
upgrading to Java 7, which might not be easy in Websphere 7, an upgrade to
Websphere 8 is another option.
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.