Controls the number of seconds to pause between the Wrapper being launched
and the first JVM being launched. Defaults to 0 seconds.
Most applications will want to maintain a startup delay of 0, but
there are some cases where system resources may not be immediately
available after a system restart for example. In general, it is
recommended to make the Java application being run, robust enough
to handle such problems. However where that is not possible, this
property may be useful.
Example: |
wrapper.startup.delay=30
|
It may be necessary to have a startup delay when running as a service
under windows. However having such a delay at all times would be
inconvenient when the application is being run from a console. The
Wrapper provides two variants of this property which make it
possible to specify different startup delays depending on whether
the Wrapper is being run as a service or a console application.
The service delay is specified using the
wrapper.startup.delay.service
property, and the console mode delay using the
wrapper.startup.delay.console
property. If either property is not specified, it defaults to
the value of wrapper.startup.delay.
Example: |
wrapper.startup.delay.console=0
wrapper.startup.delay.service=30
|
On UNIX platforms, the Wrapper is running as a service if its
wrapper.daemonize property
is set. The sh script, provided with the Wrapper, will set the
wrapper.daemonize property if the start
command is used when.
|