World Map
Java Service Wrapper is the easiest way to make your product more reliable.
  • Free Trial
  • Buy Now
wrapper.request_thread_dump_on_failed_jvm_exit Property

Index

wrapper.request_thread_dump_on_failed_jvm_exit

Compatibility :2.2.7
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

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 will have no effect if the JVM is hung for some reason as it's process will not respond to the thread dump request.

The default value is "FALSE".

Example: (Request a Thread Dump)
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.

wrapper.request_thread_dump_on_failed_jvm_exit.delay

Compatibility :3.5.6
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/OSIBM z/Linux

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.

Example: (Request a Thread Dump with long delay)
wrapper.request_thread_dump_on_failed_jvm_exit=TRUE
wrapper.request_thread_dump_on_failed_jvm_exit.delay=20

Startup-Restart: Delay