• wrapper.request_thread_dump_on_failed_jvm_exit property
• wrapper.request_thread_dump_on_failed_jvm_exit.delay property

Compatibility :	2.2.7
Editions :
Platforms :

Enabling this property will tell the Wrapper to attempt to request a Thread Dump in the event that the JVM does not exit when requested.

This information can be useful in tracking down the reason why the JVM is not exiting. This property, as well as the delay associated with it, will be ignored if the JVM is hung for some reason, as its process would not respond to the thread dump request.

The default value is "FALSE".

wrapper.request_thread_dump_on_failed_jvm_exit=TRUE

When running a Windows Service, this property will automatically allocate a console window. This is required so that the necessary signal can be sent to the JVM. When the wrapper.ntservice.console property is not explicitly set to TRUE in the configuration file, the Wrapper will hide the console.

Compatibility :	3.5.6
Editions :
Platforms :

The Wrapper needs to wait a moment after requesting a thread dump before it actually kills the JVM process. This is needed to make sure that the JVM has time to actually perform the thread dump and output it to the console or file in its entirety. This property makes it possible to control how long to wait in seconds.

The delay must be at least 1, but defaults to 5 seconds.

wrapper.request_thread_dump_on_failed_jvm_exit=TRUE
wrapper.request_thread_dump_on_failed_jvm_exit.delay=20

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