Summary

Under certain circumstances it's possible for Bitbucket Server's JAVA_HOME to be set to the embedded JRE, but for the bundled Elasticsearch's JAVA_HOME to be set to an external JRE

Expected Results

JAVA_HOME should be identical in $BITBUCKET_HOME/bin/setenv.sh and $BITBUCKET_INST/elasticsearch/bin/elasticsearch

Actual Results

Under certain circumstances, $BITBUCKET_HOME/bin/setenv.sh has JAVA_HOME set to the embedded JRE, whilst $BITBUCKET_INST/elasticsearch/bin/elasticsearch is set to an external JRE. If the external JRE is not supported (e.g. Java 1.7) then Bitbucket will start but elasticsearch will fail

Workaround

Manually update JAVA_HOME in $BITBUCKET_INST/elasticsearch/bin/elasticsearch to use the embedded JRE