Summary

When JDK11 is installed and appropriately configured on a Windows server, the Bitbucket installer still extracts and configures itself to use the bundled JRE.

Environment

• Any compatible version of Windows Server
• AdoptOpenJDK11 or other Java 11 equivalent is installed
• %JAVA_HOME% and %JRE_HOME% are both pointed to the Java 11 instance

Steps to Reproduce

1. Install AdoptOpenJDK11 on a Windows Server instance
2. Set the system environment variables JAVA_HOME and JRE_HOME to point to the installed JDK from the previous step
3. Download and run the Bitbucket Windows installer, opting to install the Windows services automatically

Expected Results

• The bundled JRE is not extracted into %BITBUCKET_INSTALL%
• The Windows Services are configured to use the configured %JRE_HOME%\bin\server\jvm.dll, which points to AdoptOpenJDK11
• The JRE_HOME value in the set-jre-home.bat script is set to where AdoptOpenJDK11 was installed

Actual Results

• The bundled JRE is extracted into the %BITBUCKET_INSTALL% directory
• The Windows Service is configured to use the bundled JRE
• The set-jre-home.bat script's JRE_HOME entry is set to use the bundled JRE

Notes

• The issue does not occur when JDK8 is installed instead. Bitbucket doesn't include the bundled JRE, and the services/scripts are configured appropriately.

Workaround

Following the installation, manually configure the Windows services to use the Java 11 instance.