Compatibility :	3.5.15
Editions :
Platforms :

When the user presses CTRL-C in a Windows console or UNIX shell, or sends a TERM signal to the Wrapper process on UNIX, the Wrapper will begin its shutdown process. This means that the Wrapper will honor all of its configured timeouts, waiting for the JVM to shutdown and exit cleanly before shutting down itself.

If the JVM is behaving poorly, or there was a misconfiguration, this means that the Wrapper could potentially take quite a while to actually shutdown. Early in the life of the Wrapper, this usability problem was identified and we added logic so that a second CTRL-C or TERM signal would tell the Wrapper to ignore all the timeouts, kill the JVM process immediately, and shutdown now. This forced shutdown will also happen if the Wrapper had already begun its shutdown process for any other reason.

While this behavior is usually very convenient, there are also times where the administrator wants to make sure that the JVM will never be forcibly shutdown in this way. This property makes it possible to disable this feature.

Since version 3.5.37 it is also possible to use the wrapper.forced_shutdown.delay property which controls the minimum amount of time required between two CTRL-C or TERM signals to initiate a forced shutdown.

• TRUE :
  to disable the forced shutdown. Any secondary requests to shutdown will be ignored.
• FALSE :
  to enable the forced shutdown. A shutdown request received when the Wrapper is already shutting down will cause the JVM to be immediately killed.

The default value is FALSE.

wrapper.disable_forced_shutdown=TRUE

wrapper  | CTRL-C trapped.  Shutting down.
wrapper  | CTRL-C trapped.  Forcing immediate shutdown.
wrapper  | JVM did not exit on request, terminated
wrapper  | <-- Wrapper Stopped

wrapper  | CTRL-C trapped.  Shutting down.
wrapper  | CTRL-C trapped.  Already shutting down.
wrapper  | ...
wrapper  | <-- Wrapper Stopped

If forced shutdowns have been disabled and the wrapper.shutdown.timeout or wrapper.jvm_exit.timeout properties are set to long values, you may need to wait for both timeouts to complete before the Wrapper will shutdown. In this case, the only way to speed up the shutdown is to forcibly kill the Java process using the Task Manager on Windows, or a kill -9 on UNIX. Note that on some versions of Windows, it is not possible to kill Java from the Task Manager when running as a service.

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.