# Installation Doc:

**URL:** https://discuss.elastic.co/t/installation-doc/8953
**Category:** Elasticsearch
**Created:** [September 7, 2012, 1:38pm UTC](https://discuss.elastic.co/t/installation-doc/8953 "2012-09-07T13:38:37Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![BillyEm](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@BillyEm](https://discuss.elastic.co/u/BillyEm)
#### Post date: [September 7, 2012, 1:38pm UTC](https://discuss.elastic.co/t/installation-doc/8953/1 "2012-09-07T13:38:37Z")

</div>

A recent bug fix illustrates that if JAVA\_HOME is not defined at startup,  
the system uses whatever it can find with "whatever?" path it is using.  
Note the following insufficient documentation statement:

\*The version of Java that will be used can be set by setting the JAVA\_HOMEenvironment variable.  
\*

Its not acceptable that an Enterprise shop should have dig through source  
code to determine why this isn't working. Hence I suggest the following  
change: someone open an issue on the dev community requesting that 1) is  
JAVA\_HOME is found it is declared in the logs, and the version is printed,  
2) if note found, message again with the location of the java that _was_  
found and print its version.

I have decades of experience with enterprise search shops; and search shops  
alone. This doesn't meet my need for certifying to Network Ops.

? thoughts ?

--

---

<div class="post-metadata">

### Author: ![Rafal\_Kuc\_3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafal_kuc_3/32/799_2.png) [@Rafal\_Kuc\_3](https://discuss.elastic.co/u/Rafal_Kuc_3)
#### Post date: [September 7, 2012, 1:44pm UTC](https://discuss.elastic.co/t/installation-doc/8953/2 "2012-09-07T13:44:01Z")

</div>

Hello!

What wait for someone to open the issue, when you can do it yourself ? Just to to [https://github.com/elasticsearch/elasticsearch/issues](https://github.com/elasticsearch/elasticsearch/issues) and create a new issue there.

_--_

Regards,

Rafał Kuć

Sematext :: [http://sematext.com/](http://sematext.com/) _:: Solr - Lucene - Nutch - ElasticSearch_

A recent bug fix illustrates that if JAVA\_HOME is not defined at startup, the system uses whatever it can find with "whatever?" path it is using. Note the following insufficient documentation statement:

_The version of Java that will be used can be set by setting the JAVA\_HOME environment variable._

Its not acceptable that an Enterprise shop should have dig through source code to determine why this isn't working. Hence I suggest the following change: someone open an issue on the dev community requesting that 1) is JAVA\_HOME is found it is declared in the logs, and the version is printed, 2) if note found, message again with the location of the java that _was_ found and print its version.

I have decades of experience with enterprise search shops; and search shops alone. This doesn't meet my need for certifying to Network Ops.

? thoughts ?

--

---

<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 6, 2017, 3:13am UTC](https://discuss.elastic.co/t/installation-doc/8953/3 "2017-07-06T03:13:47Z")

</div>


