# Embedded Elasticseach and IBM JDK **URL:** \ **Category:** Elasticsearch\ **Created:** [December 17, 2012, 9:44am UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089 "2012-12-17T09:44:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Runar\_Myklebust\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/runar_myklebust_2/32/2047_2.png) [@Runar\_Myklebust\_2](https://discuss.elastic.co/u/Runar_Myklebust_2)\ **Post date:** [December 17, 2012, 9:44am UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089/1 "2012-12-17T09:44:07Z")
Hi. 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. Is this a known issue? -- Runar Myklebust Enonic AS Senior Developer [http://enonic.com/download](http://enonic.com/download) -- ---
**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\ **Post date:** [December 18, 2012, 2:29pm UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089/2 "2012-12-18T14:29:38Z")
This is most likely a Lucene and jvm combination issue. Can you ask the client to upgrade their jvm. Martijn On 17 December 2012 10:44, Runar Myklebust [runar@myklebust.me](mailto:runar@myklebust.me) wrote: > Hi. > > 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. > > Is this a known issue? > > -- > Runar Myklebust > Enonic AS > Senior Developer > > [http://enonic.com/download](http://enonic.com/download) > > -- -- Met vriendelijke groet, Martijn van Groningen -- ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 18, 2012, 8:56pm UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089/3 "2012-12-18T20:56:00Z")
Hi Runar, can you show the complete error message? What is the service release of the IBM JVM? 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. Best regards, Jörg -- ---
**Author:** ![Runar\_Myklebust\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/runar_myklebust_2/32/2047_2.png) [@Runar\_Myklebust\_2](https://discuss.elastic.co/u/Runar_Myklebust_2)\ **Post date:** [December 18, 2012, 10:24pm UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089/4 "2012-12-18T22:24:51Z")
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. On Tue, Dec 18, 2012 at 9:56 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hi Runar, > > can you show the complete error message? > > What is the service release of the IBM JVM? > > 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. > > Best regards, > > Jörg > > -- -- Runar Myklebust Enonic AS Senior Developer [http://enonic.com/download](http://enonic.com/download) -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:59am UTC](https://discuss.elastic.co/t/embedded-elasticseach-and-ibm-jdk/10089/5 "2017-07-06T02:59:24Z")