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.
Causes the Wrapper to create an anchor file on startup.
This property is not set by default.
The Wrapper will monitor the file and then shutdown when it is deleted.
The Wrapper can still be shutdown by normal methods.
If the anchor file still exists when the Wrapper shuts down,
it will be deleted automatically.
Common values are
./myapp.anchor or
/var/run/myapp.anchor.
Example:
wrapper.anchorfile=wrapper.anchor
While the property is supported on all platforms,
it is most commonly used in combination with the
wrapper.ignore_signals
property on Unix systems.
In such cases, rather than setting either of these properties manually,
it is suggested that the IGNORE_SIGNALS property
be uncommented in the shell script which is shipped with the Wrapper.
See the wrapper.ignore_signals
property for further details.
NOTE
Reloading the configuration
will NOT enable to take effect on the value of this property.
The Wrapper is required to restart in order to make the changes effective.
wrapper.anchor.poll_interval
The interval at which the existence of the anchor file is tested can be controlled using the
wrapper.anchor.poll_interval property.
Defaults to 5 seconds, with valid values in the range of 1 to 3600 seconds.
Example:
wrapper.anchor.poll_interval=5
NOTE
Reloading the configuration
will NOT enable to take effect on the value of this property.
The Wrapper is required to restart in order to make the changes effective.
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.
