# Upgrade to elasticsearch 1.6.0 - JVM incompatibility

**URL:** <https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279>\
**Category:** Elasticsearch\
**Created:** [July 10, 2015, 4:13am UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279 "2015-07-10T04:13:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kkomv](https://avatars.discourse-cdn.com/v4/letter/k/838e76/32.png) [@kkomv](https://discuss.elastic.co/u/kkomv)\
**Post date:** [July 10, 2015, 4:13am UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279/1 "2015-07-10T04:13:25Z")

</div>

Installation is failing with the below error ,

{1.6.0}: Initialization Failed ...

- RuntimeException[Java version: 1.7.0\_51 suffers from critical bug [https://bugs.openjdk.java.net/browse/JDK-8024830](https://bugs.openjdk.java.net/browse/JDK-8024830) which can cause data corruption [https://bugs.openjdk.java.net/browse/JDK-8024830%20which%20can%20cause%20data%20corruption](https://bugs.openjdk.java.net/browse/JDK-8024830%20which%20can%20cause%20data%20corruption) .  
Please upgrade the JVM, see [http://www.elastic.co/guide/en/elasticsearch/reference/current/\_installation.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/_installation.html) for current recommendations.  
If you absolutely cannot upgrade, please add -XX:-UseSuperWord to the JVM\_OPTS environment variable.  
Upgrading is preferred, this workaround will result in degraded performance.]

our current java version is

_java version "1.7.0\_51"_  
_Java(TM) SE Runtime Environment (build 1.7.0\_51-b13)_

**What should be the minimum required JVM version that we need to upgrade to on java 1.7, cannot move to java 1.8**

---

<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:** [July 10, 2015, 4:20am UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279/2 "2015-07-10T04:20:30Z")

</div>

1.7u55 and above, per [https://www.elastic.co/subscriptions/matrix](https://www.elastic.co/subscriptions/matrix)

---

<div class="post-metadata">

**Author:** ![kkomv](https://avatars.discourse-cdn.com/v4/letter/k/838e76/32.png) [@kkomv](https://discuss.elastic.co/u/kkomv)\
**Post date:** [July 14, 2015, 6:45pm UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279/3 "2015-07-14T18:45:02Z")

</div>

Thanks Mark, how do I make elasticsearch to use the upgraded jre which is installed at a different path and not the one at JAVA\_HOME. The existing 1.7.0\_51 JRE at JAVA\_HOME is used by several other java processes on this server and do not want to impact them.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [July 14, 2015, 7:00pm UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279/4 "2015-07-14T19:00:25Z")

</div>

Its different depending on how you've installed Elasticsearch. If you used the .deb you put it in /etc/defaults/elasticsearch as

```bash
JAVA_HOME=/usr/share/SOME_OTHER_JAVA

```

---

<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:56pm UTC](https://discuss.elastic.co/t/upgrade-to-elasticsearch-1-6-0-jvm-incompatibility/25279/6 "2017-07-05T23:56:57Z")

</div>