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.restart.delay=30
|
Especially on Windows, it may be necessary to have a startup delay
when running as an NT service, but when running as a console
application. The Wrapper makes this possible with the following
two variants of this property. They both default to the value of
wrapper.startup.delay
Example: |
wrapper.restart.delay.console=0
wrapper.restart.delay.service=30
|
On UNIX platforms, the Wrapper is running as a service if its
wrapper.daemonize property
is set. If the sh script, provided with the Wrapper, will set this
property if the start command
is used when.
|