DO NOT modify the value of these properties
while an application using the configuration file has been installed as a Windows Service.
Please uninstall the existing service BEFORE modifying this property.
The service with the new value can then be safely reinstalled later.
The Wrapper can be configured to launch a JVM that has been configured in the Windows registry.
property is required to be set to an empty value.
If the Java command is located using the Windows registry,
the path to the command will be stored into a
WRAPPER_JAVA_HOME environment variable.
This value can then be referenced in the values of other properties.
The following properties can be used to configure how to search in the Windows Registry.
If none of them are set, the Wrapper will use the 'CurrentVersion' string of the Registry.
Oracle changed the location of the registry keys for JRE versions 9 and above,
so there can be two 'CurrentVersion' strings if old and recent versions coexist on the machine.
By default the Wrapper will try using the current version of recent JRE installations (9 and above).
Failing that, it will search for the current version of older JRE installations.
By default, the Wrapper will look for a registry entry set by the Sun JRE installer.
This property makes it possible to tell the Wrapper to look in a specific location
for a registry key containing a JAVA_HOME value.
The registry entry should contain a fully qualified, absolute path to a Java installation.
It should be the home directory of the installation.
The Wrapper will append \bin\java to the specified directory.
Example - REG_SZ Value:
This property can be used as an alternative to wrapper.registry.java_home
to specify a version of the JRE to use when the Java command is located using the Windows registry.
The Wrapper will look for the specified version contained in the registry key set by the JRE installer.
If no match could be found, the Wrapper will stop with an error.