Google

Locations of visitors to this page

Hosted by:
SourceForge

wrapper.thread_dump_control_code Property
wrapper.thread_dump_control_code Property
Configuration Property Overview
wrapper.thread_dump_control_code

The Wrapper is able to initiate a thread dump in response to a user defined control code when running as a service. This property makes it possible to specify which code to use, or even to disable this feature, to meet the needs of a specific application. Valid values are 128 - 255, or 0 to disable. Defaults to 255.

Example:
wrapper.thread_dump_control_code=255

It is only possible to request thread dumps using service control codes when the service is running as a Windows service. This property has no effect when running in console mode.

There are three ways to initiate a thread dump on a running service using the control code.

The first is to use Wrapper's dump command as follows:

Example:
wrapper.exe -d ..\conf\wrapper.conf

The second is to use Wrapper's ability to send an arbitrary service command as follows:

Example:
wrapper.exe -l=255 ..\conf\wrapper.conf

The third is to use standard Windows commandline tools to send the code:

Example:
sc control myapp 255

It is also possible to send the control code programatically using the appropriate windows APIs.



User Comments

If you notice something that is incorrect, missing, or simply feel that some part of this page could be explained better, feel free to log in and add a comment. You will need to register before you can log on.

Email:
Password:
last modified: