Compatibility :	3.5.37
Editions :
Platforms :

This property is only effective when wrapper.disabled_forced_shutdown it set to FALSE. It controls the minimum amount of time required between two CTRL-C or TERM signals to initiate a forced shutdown.

The unit value for this property is 100ms.

The default value is 2 (200ms) to prevent double signals from forcibly shutting down the application.

wrapper.forced_shutdown.delay=0

wrapper.forced_shutdown.delay=5

The Java Service Wrapper provides a full set of configuration properties that allows you to make the Wrapper meet your exact needs. Please take a look at the documentation for the individual properties to see all of the possibilities beyond the examples shown above.

• wrapper.anchorfile (3.1.1)

  Sets the path to an anchor file created on startup.

• wrapper.check.deadlock.action (3.5.0) ( Std/Pro )

  Configures the actions to take place whenever deadlocks are detected.

• wrapper.commandfile (3.2.0)

  Sets the path to a file containing commands to be executed.

• wrapper.disable_shutdown_hook (1.0.0)

  Disables detection of calls to System.exit().

• wrapper.disable_forced_shutdown (3.5.15)

  Disables forced shutdowns in a Windows console or UNIX shell.

• wrapper.forced_shutdown.delay (3.5.37)

  Controls the minimum amount of time required between two CTRL-C or TERM signals to initiate a forced shutdown.

• wrapper.event.<event_name>.command.block.action (3.4.1) ( Pro )

  Configures the action to take place whenever a configured event command fails to complete within the specified timeout.

• wrapper.exit_code.error (3.5.31)

  Specifies the exit code to use when the Wrapper stops with an error.

• wrapper.filter.action.<n> (3.0.0)

  Configure the actions to take place whenever filters are triggered.

• wrapper.filter.trigger.<n> (3.0.0)

  Specify the texts to trigger actions when matching a log message.

• wrapper.ignore_signals (3.0.5)

  Controls whether or not the Wrapper should ignore system signals.

• wrapper.jvm_exit.timeout (2.2.8)

  Configures the number of seconds to allow between the time the JVM reports it is stopped and the time the JVM process actually terminates.

• wrapper.on_exit.<n> (3.1.0)

  Configure the actions to take place when the Java application exits with the specified exit codes.

• wrapper.pidfile (3.5.14)

  Sets the path to a file where the PID of the Wrapper process will be written.

• wrapper.shutdown.timeout (2.2.7)

  Configures the number of seconds to allow between the time the Wrapper asks the JVM to shutdown and the time the JVM responds that it is stopping.

• wrapper.timer.<n>.action (3.3.0) ( Pro )

  Configure the actions to take place whenever timers are fired.