Hosted by:

wrapper.request_thread_dump_on_failed_jvm_exit Property

wrapper.request_thread_dump_on_failed_jvm_exit Property

Configuration Property Overview

- Configuration Property Overview
- Advanced Properties
- Property List by Name

wrapper.request_thread_dump_on_failed_jvm_exit

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

Example:

    wrapper.request_thread_dump_on_failed_jvm_exit=TRUE

When running an NT service, this property will automatically set the wrapper.ntservice.console property to true. This is required so that the necessary signal can be sent to the JVM. When the wrapper.ntservice.console is not explicitly set to true in the configuration file, the Wrapper will hide the console immediately after it is displayed. This will cause a noticeable flicker on the screen when the Wrapper is first started.

NOTE MEG |  | If any Windows API gurus out there can figure out a way to allocate a console without it being displayed on the screen, I would love to hear about it so that I can get rid if the flicker.

by Leif Mortenson

Copyright ©1999-2004 by Tanuki Software. All Rights Reserved. | last modified: