Compatibility :	2.2.9
Editions :
Platforms :

This property controls the number of seconds to pause between a JVM exiting for any reason, and a new JVM being launched. The default value is "5 seconds".

Setting this restart delay to a very low value or even "0" (zero) could cause problems as the new JVM could may be launched before all resources from the previous invocation have been reclaimed by the OS (operating system).

wrapper.restart.delay=5

• 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 )

  Configure 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.