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.
Lock file containing the Wrapper's process ID.
This property is not set by default.
If this property is set, a file containing the pid of the Wrapper process
will be written to the specified location when the process is launched.
The file will be deleted when the Wrapper process has terminated.
A common value is /var/lock/subsys/myapp.
If a second instance of the Wrapper is started,
the lock file of the first instance will be overwritten by the second instance.
This is done to avoid problems with stale lock files preventing the Wrapper from starting.
On Linux/UNIX platforms, the shell script (sh)
which is shipped with the Wrapper will prevent multiple copies of
the Wrapper from running for the same application.
It is possible to run multiple copies of the Wrapper on the same machine
if some of Wrapper are each being used to launch a different application.
In most cases, users will not need to set this property themselves.
The UNIX shell script (sh)
which is shipped with the Wrapper
sets this property from the command line
and then makes use of the lock file in future invocations of the script.
App.sh.in file in the
src/bin directory for an example (on older Wrapper versions, this file was named 'sh.script.in').
The property is also available in the Windows version.
If the specified file can not be written for any reason on startup,
a warning message will be logged
but the Wrapper will continue to start up.
Changes to the value of this property will not have any affect on the Wrapper
if the configuration is reloaded.
The Wrapper must be restarted for changes to take effect.