Compatibility :	3.5.5
Editions :
Platforms :

The Windows Service Control Manager maintains a failure count for each service installed. Every time the service terminates unexpectedly, the counter will be incremented and the registered failure action for that count will be triggered.

This property is used to configure the time in seconds, without any errors, after which the Service Manager will reset this counter back to "0" (zero). The default value for this property is 3600 (= 1 hour). If "-1" is set, this means that the Service Control Manager will never reset the counter.

wrapper.ntservice.recovery.reset=86400

Compatibility :	3.5.5
Editions :
Platforms :

One thing that the Service Control Manager lets you do is execute an external command in response to a failure. This can be used to do things like perform cleanup or send external notification.

While it is possible to specify a different wrapper.ntservice.recovery.<n>.failure property for each recovery event, the Service Control Manager API only makes it possible to specify a single command, which can then be referenced as the failure action for one or more recovery event.

This property does not have a default value and must be specified if one or more "failure actions" (wrapper.ntservice.recovery.<n>.failure property) is set to COMMAND.

wrapper.ntservice.recovery.command=C:\cleanup.bat

Compatibility :	3.5.5
Editions :
Platforms :

If REBOOT is specified for a wrapper.ntservice.recovery.<n>.failure property, the Service Control Manager will log a System Event describing "why the system was rebooted". This property is used to define the text of that message.

The default message is localized based language the Wrapper is running as. For English, the default is: "System will be rebooted now due to an error in the wrapped service."

wrapper.ntservice.recovery.reboot_msg=System will reboot now.

Compatibility :	3.5.5
Editions :
Platforms :

This property sets the failure action which should happen if the Wrapper service crashes or exits with an error. The "<n>" component of the property name indicates the number of the failure count.

The Service Control Manager counts the number of times each service has failed since the system booted. The count is reset back to "0" (zero) if the service has not failed for at least wrapper.ntservice.recovery.reset seconds. When the service fails, the failure count (N) is used to decide which failure action to take. These actions are defined with the wrapper.ntservice.recovery.<n>.failure property, where 'N' is the failure count. If N is greater than the last configured action, then the failure action with the highest N (<n> index) will be used.

Possible actions are:

• NONE :

  The Service Manager will do nothing. This is the same as if no recovery properties were specified. The service will stop and stay stopped. Any failure actions defined with higher N values will never be reached.

• RESTART :

  The Service Manager will restart the service. This is the most commonly used action with the Wrapper as the Wrapper itself is capable of cleaning up after the JVM after a failure.

• COMMAND :

  The Service Manager will run the command specified with the wrapper.ntservice.recovery.command property. If you wish the service to be restarted after running the command then this must be done within the command.

• REBOOT :

  The Service Manager will reboot the machine. If the service's "start" mode is set to AUTO_START, then the service will be started again after the reboot. See the wrapper.ntservice.starttype property for more information.

wrapper.ntservice.recovery.1.failure=RESTART
wrapper.ntservice.recovery.2.failure=COMMAND
wrapper.ntservice.recovery.3.failure=REBOOT

While the API makes it possible to specify a failure action after NONE or REBOOT, they will never be used.

Compatibility :	3.5.5
Editions :
Platforms :

This property sets the time in seconds the Service Control Manager will wait until it actually performs the according action specified in wrapper.ntservice.recovery.<n>.failure.

The value of this property can not be smaller than "0" (zero). The default value is 3 times the value of wrapper.ping.timeout property. If the Wrapper process itself were to crash while the JVM was still up and running, the JVM is configured to shut itself down after the 3 times the ping timeout. This recovery delay uses the same value to avoid restarting the Wrapper with a second JVM until the first has had a chance to shutdown. Starting a second JVM would most likely cause resource conflicts.

While in theory it would be possible to set a delay for the failure action "NONE", the Service Control Manager would ignore the delay in this case.

wrapper.ntservice.recovery.1.delay=90