• wrapper.java.command property
• wrapper.java.command.resolve property

Compatibility :	1.0.0
Editions :
Platforms :

The command to use when launching a JVM. If the full path to the Java executable is not specified, then the Wrapper will attempt to locate a Java executable on the system path.

wrapper.java.command=java

wrapper.java.command=%JAVA_HOME%/bin/java

wrapper.java.command=c:/j2sdk1.4.0/bin/java

Not contain an extension:

It is advised that the value does not contain an extension. Specifying a value like java.exe together with an extension would mean that the same configuration file could not be used on Linux/UNIX systems.

Windows:

On Windows systems, it is also possible to use the JRE configuration from the system registry. In that case, this property is required to be set to an empty value.

By default, the Wrapper will look for the Sun JRE specified in the default registry key. It is possible to configure a specific JAVA_HOME location using the wrapper.registry.java_home property.

wrapper.java.command=

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.

Compatibility :	3.5.4
Editions :
Platforms :

This property specifies whether the Wrapper should try to resolve the Java command specified in the wrapper.java.command property or continue using the unresolved path as possibly defined.

Resolving the Java command by the Wrapper is generally a good option, as it will help you to point out and start troubleshooting easily missettings on the environment leading to unexpected behaviour when starting your application with the Wrapper. However, on some UNIX distributions a JVM can be started not only with the "java" command but also by small helper applications, e.g. run-java-tool on Gentoo Linux. However this application might only allow to get called via a symbolic link to them.

The default value of this property is "TRUE". If you want to deactivate the resolving, please switch this property to FALSE.

wrapper.java.command.resolve=true

• wrapper.java.command (1.0.0)

  Sets the path to the Java executable.

• wrapper.java.command.resolve (1.0.0)

  Specifies whether the Wrapper should try to resolve the specified Java command or continue using the unresolved path as possibly defined.

• wrapper.java.command.loglevel (3.1.2)

  Controls at which log level the generated command line will be logged.

• wrapper.java.detect_debug_jvm (3.3.6)

  Enables the detection of a debugger in the command line.

• wrapper.java.version.fallback (3.5.38)

  Specifies a fallback value to be used when the Java version failed to be parsed.

• wrapper.java.version.max (3.5.35)

  Specifies the maximum version of Java for which the Wrapper is allowed to launch the Java Application.

• wrapper.java.version.min (3.5.35)

  Specifies the minimum version of Java for which the Wrapper is allowed to launch the Java Application.

• wrapper.java.version.output (3.5.17)

  Displays the version of the JVM used by the Wrapper.

• wrapper.java.version.timeout (3.5.27)

  Configures the number of seconds allowed for the child process to print the JVM version before it is terminated.

• wrapper.registry.java_home (3.2.4)

  Specifies a registry key containing the path to the Java home folder.

• wrapper.registry.java_version (3.5.36) ( Std/Pro )

  Specifies a version of the JRE to use when locating the Java command from the Windows registry.