Compatibility :	3.1.0
Editions :
Platforms :

This property controls the number of seconds to pause between the Wrapper being launched and the first JVM being launched. The default value is "0" (zero) seconds.

Most applications will want to maintain a startup delay of "0" (zero) seconds, 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.

wrapper.startup.delay=30

Compatibility :	3.1.0
Editions :
Platforms :

It may be necessary to have a startup delay when running as a service or as a console application. 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.
• 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 above.

wrapper.startup.delay.console=0
wrapper.startup.delay.service=30

On Linux/UNIX platforms, the Wrapper is running as a service if its wrapper.daemonize property is set to TRUE. The shell script, shipped with the Wrapper, will set the wrapper.daemonize property if the start command is being used.

• wrapper.restart.delay (2.2.9)

  Controls the number of seconds to wait between a JVM exiting and a new JVM being launched.

• wrapper.startup.delay (3.1.0)

  Controls the number of seconds to wait between the Wrapper being launched and the first JVM being launched.

• wrapper.startup.delay.console (3.1.0)

  Overrides wrapper.startup.delay when running as a console application.

• wrapper.startup.delay.service (3.1.0)

  Overrides wrapper.startup.delay when running as a service.

• wrapper.request_thread_dump_on_failed_jvm_exit.delay (3.5.6)

  Configures the number of seconds allowed for the thread dump to complete before killing the JVM process.

• wrapper.ntservice.recovery.<n>.delay (3.5.5) ( Std/Pro )

  Configures the maximum number of seconds that the service control manager should wait before performing an action after <n> failures.

• wrapper.jvm_kill.delay (3.5.6) ( Pro )

  Configures the number of seconds to pause between firing a JVM kill event and actually killing it.