Hosted by:
SourceForge

wrapper.lockfile Property
wrapper.lockfile Property
Configuration Property Overview
wrapper.lockfile

Lock file containing the Wrapper's process ID. If 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. This property is not set by default. A common value is /var/lock/subsys/myapp.

NOTE

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 Unix/Linux platforms, the sh script which ships 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 they are each being used to launch a different application.

In most cases, users will not need to set this property themselves. The Unix sh script which ship with the Wrapper sets this property from the command line and then makes use of the lock file in future invocations of the script. See the sh.script.in file in the src/bin directory for an example.

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.

The property is also available in the Windows version.

Example:
wrapper.pidfile=/var/lock/subsys/myapp

NOTE

Reloading the Wrapper configuration will have no effect on the value of this property. Changes will not take effect until the Wrapper has been restarted.

by Leif Mortenson

last modified: