wrapper.test.no_jvm
Compatibilidad :3.5.35
Ediciones :Edición ProfesionaEdición EstándarEdición de la Comunidad
Plataformas :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/Linux

Sometimes it can be useful to test the Wrapper configuration or check the Wrapper outputs without launching a JVM. When this property is set to TRUE, the Wrapper will run until it is about to launch a JVM, and then will shutdown.

The default value is FALSE.

Here are few examples in which this property can be used:

Check the license status: 
wrapper.license.debug=TRUE
wrapper.test.no_jvm=TRUE

Check the configuration (print a warning whenever a property is overwritten and display information about the configuration properties): 
#properties.on_overwrite.loglevel=WARN
wrapper.properties.dump.loglevel=INFO
wrapper.properties.dump.format=ZCLFINV
wrapper.test.no_jvm=TRUE

Visualize environment variables: 
wrapper.environment.dump.loglevel=INFO
wrapper.test.no_jvm=TRUE

Confirm the Java version used by the Wrapper: 
wrapper.java.version.output=TRUE
wrapper.test.no_jvm=TRUE

Visualize the Java command line (without executing it): 
wrapper.java.command.loglevel=INFO
wrapper.test.no_jvm=TRUE

Print all debug output: 
wrapper.debug=TRUE
wrapper.test.no_jvm=TRUE

NOTA

It is generally a good practice to specify this property directly in the command line used to launch the Wrapper, to avoid the risk of leaving it in the configuration file. If you need to test a configuration specific to a Windows Service, please be aware that command line properties don't apply when starting the service and should be specified when installing it. In this case, it may be easier to just set this property in the configuration file.