Configuration Property Overview

wrapper.restart.reload_configuration

Compatibility :	3.2.0
Editions :
Platforms :

WARNING

DO NOT modify any of these parameters unless you have read this property description. Incorrect settings can cause the Wrapper to fail to operate as expected.

This property controls whether or not the Wrapper configuration file will be reloaded in the event of a JVM restart. The default value is "FALSE".

Example:
wrapper.restart.reload_configuration=TRUE

This property can be useful when an application needs to modify its own configuration and enable to be effective on its restart. An example would be adding downloaded jars to the classpath and then restarting.

If portions of the configuration need to be created dynamically, consider making use of the #include cascading syntax in the main configuration file and then writing the dynamic values to a separate file. This can greatly simplify the generation of that section of the configuration.

NOTE

The Wrapper will not reload the configuration file on a JVM restart unless this property is set to TRUE. It is possible to enable the reloading of the configuration only when the Wrapper is restarted.

It is possible to disable configuration reloading by setting the property value to "FALSE" or removing the property all together. But be aware that once this has been done and the JVM restarted, it will not be possible to reenable the configuration reloading unless the Wrapper itself is restarted.

NOTE

The feature of "Reloading the configuration" will NOT enable to take effect on the value of the following properties:

User Comments

If you notice something that is incorrect, missing, or simply feel that some part of this page could be explained better, feel free to log in and add a comment. You will need to register before you can log on.

Java Service Wrapper Version: 3.5.4