# JDK for ElasticStack

**URL:** <https://discuss.elastic.co/t/jdk-for-elasticstack/189973>\
**Category:** Elasticsearch\
**Created:** [July 11, 2019, 10:28am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973 "2019-07-11T10:28:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjabiulla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjabiulla/32/48429_2.png) [@sjabiulla](https://discuss.elastic.co/u/sjabiulla)\
**Post date:** [July 11, 2019, 10:28am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/1 "2019-07-11T10:28:11Z")

</div>

I have downloaded latest Elastic search for windows and I can see that JDK folder is available in the ElasticSearch folder. Does this mean that we don't need to depend on external jdk for whole Elastic Stack ?

Since ElasticStack depends on Java, How does Oracle JDK Licensing affect the users using Elastic Stack ?

---

<div class="post-metadata">

**Author:** ![ylasri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ylasri/32/86120_2.png) [@ylasri](https://discuss.elastic.co/u/ylasri)\
**Post date:** [July 11, 2019, 10:42am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/2 "2019-07-11T10:42:55Z")

</div>

## 

Java (JVM) Version ([https://github.com/elastic/elasticsearch/edit/7.2/docs/reference/setup.asciidoc](https://github.com/elastic/elasticsearch/edit/7.2/docs/reference/setup.asciidoc))

Elasticsearch is built using Java, and includes a bundled version of [OpenJDK](http://openjdk.java.net/) from the JDK maintainers (GPLv2+CE) within each distribution. The bundled JVM is the recommended JVM and is located within the `jdk` directory of the Elasticsearch home directory.

To use your own version of Java, set the `JAVA_HOME` environment variable. If you must use a version of Java that is different from the bundled JVM, we recommend using a [supported](https://www.elastic.co/support/matrix) [LTS version of Java](http://www.oracle.com/technetwork/java/eol-135779.html). Elasticsearch will refuse to start if a known-bad version of Java is used. The bundled JVM directory may be removed when using your own JVM.

---

<div class="post-metadata">

**Author:** ![sjabiulla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjabiulla/32/48429_2.png) [@sjabiulla](https://discuss.elastic.co/u/sjabiulla)\
**Post date:** [July 11, 2019, 10:49am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/3 "2019-07-11T10:49:25Z")

</div>

Thanks for the info.

Is it recommended to use the bundled JVM ( located within the `jdk` directory of the Elasticsearch home directory) in production or Would you suggest us to use our own version of Java for Production instances !!

---

<div class="post-metadata">

**Author:** ![ylasri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ylasri/32/86120_2.png) [@ylasri](https://discuss.elastic.co/u/ylasri)\
**Post date:** [July 11, 2019, 11:18am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/4 "2019-07-11T11:18:35Z")

</div>

We use bundled JVM in production for all our customers.  
Also all dev are based on openJDK

---

<div class="post-metadata">

**Author:** ![sjabiulla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjabiulla/32/48429_2.png) [@sjabiulla](https://discuss.elastic.co/u/sjabiulla)\
**Post date:** [July 11, 2019, 11:58am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/5 "2019-07-11T11:58:17Z")

</div>

ok. thank you

---

<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:** [August 8, 2019, 11:58am UTC](https://discuss.elastic.co/t/jdk-for-elasticstack/189973/6 "2019-08-08T11:58:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.