# IBM jdk problems with Elasticsearch

**URL:** <https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104>\
**Category:** Elasticsearch\
**Created:** [February 18, 2016, 6:08am UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104 "2016-02-18T06:08:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![punit\_naik1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/punit_naik1/32/7239_2.png) [@punit\_naik1](https://discuss.elastic.co/u/punit_naik1)\
**Post date:** [February 18, 2016, 6:08am UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104/1 "2016-02-18T06:08:50Z")

</div>

I am using IBM jdk on my power PC and running an Elasticsearch instance. But he problem is, when I start Elsaticsearch, it guves me th efollowing message in the log file and terminates:

`IBM runtimes suffer from several bugs which can cause data corruption. Please upgrade the JVM.`

So the problem is, IBM jdk is failing the JVM check.

What do I do?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 18, 2016, 6:16am UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104/2 "2016-02-18T06:16:01Z")

</div>

We don't support this JVM, you will need to pick another one - [https://www.elastic.co/support/matrix#show\_jvm](https://www.elastic.co/support/matrix#show_jvm)

---

<div class="post-metadata">

**Author:** ![punit\_naik1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/punit_naik1/32/7239_2.png) [@punit\_naik1](https://discuss.elastic.co/u/punit_naik1)\
**Post date:** [February 18, 2016, 7:26am UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104/3 "2016-02-18T07:26:00Z")

</div>

@warkolm Okay. But I added `-Des.bypass.vm.check=true` JVM option to elasticsearch command line while starting and it works fine now. So my question is, will I have to worry about its proper working in the future?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 18, 2016, 7:24pm UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104/4 "2016-02-18T19:24:26Z")

</div>

As far as I understand there are no plans to support this JDK.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:15pm UTC](https://discuss.elastic.co/t/ibm-jdk-problems-with-elasticsearch/42104/5 "2017-07-05T23:15:10Z")

</div>