Compatibility :	3.5.6
Editions :
Platforms :

This property controls the number of seconds to pause between firing the jvm_kill event, and actually killing the JVM.

The default value is "0" (zero) seconds.

wrapper.jvm_kill.delay=0

When the Wrapper decides to kill the JVM, some applications will first want to execute an external command to something with the JVM before it is killed. This is accomplished using the one of "event command" (wrapper.event.<event_name>.command.argv.<n>) property and the jvm_kill event. While it is possible to set the wrapper.event.<event_name>.command.block property to make sure that the command completes before continuing, some applications would still have timing issues that require additional time.

The Wrapper can be configured to request a thread dump before killing the JVM using the internal wrapper.request_thread_dump_on_failed_jvm_exit property. However, as an example, this can also be done by executing a command in response to the jvm_kill event.

Unix:

On UNIX, a thread dump can also be invoked by sending a SIGQUIT signal to the JVM process. The jvm_kill event takes place immediately before the JVM process is killed. This means that the JVM will likely have already been killed by the time the signal is actually sent. To work around this timing problem, we add a 5 second delay between the execution of the external command and the Wrapper actually killing the JVM.

wrapper.jvm_kill.delay=5
wrapper.event.jvm_kill.command.loglevel=INFO
wrapper.event.jvm_kill.command.argv.1=kill
wrapper.event.jvm_kill.command.argv.2=-SIGQUIT
wrapper.event.jvm_kill.command.argv.3=%WRAPPER_EVENT_JVM_PID%

Windows:

This could also be done on Windows when running as a service. The following example assumes that the service is named "MyApp". The "255" needs to match the value of the wrapper.thread_dump_control_code property.

wrapper.jvm_kill.delay=5
wrapper.event.jvm_kill.command.loglevel=INFO
wrapper.event.jvm_kill.command.argv.1=sc
wrapper.event.jvm_kill.command.argv.2=control
wrapper.event.jvm_kill.command.argv.3="MyApp"
wrapper.event.jvm_kill.command.argv.4=255

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