Compatibility :	3.5.18
Editions :
Platforms :

Number of seconds to allow between the time that the Wrapper asks the system to forcibly terminate the JVM process and the time that the Wrapper verifies that the JVM has actually been terminated. Setting this property value to "0" (zero) means never time out.

The default value is "10 seconds".

wrapper.jvm_terminate.timeout=10

In most cases this property should not need to be adjusted. Setting it too short could have adverse affects.

In almost all cases the system will be able to forcibly terminate a process, assuming it has access to do so. We received reports from a couple users on Windows where a request to terminate a frozen JVM process was returning successfully, but the JVM process was never actually being terminated. This unfortunately is an unrecoverable state for the Wrapper. Implementation of this property was done to allow the Wrapper to accurately explain the problem in the logs and then shutdown cleanly.

wrapper  | Timed out waiting for the OS to forcibly terminate the JVM process, unable to continue.
wrapper  |   The scheduled restart of the JVM has been cancelled.

If you see this problem, please contact support about it as we are interested in finding an environment where it can be reproduced reliably.

• wrapper.cpu.timeout (2.2.8)

  Configures the number of seconds without CPU before the JVM sends a warning and extend timeouts.

• wrapper.max_hostid_timeout (3.4.0) ( Std/Pro )

• wrapper.logfile.close.timeout (3.5.21)

  Controls the number of seconds at which the log file should close after the last log entry.

• wrapper.logfile.flush.timeout (3.5.21)

  Configures the interval in seconds at which the Wrapper flushes all outputs to the log file.

• wrapper.logfile.inactivity.timeout (3.2.0, deprecated as of 3.5.21)

  Controls the number of seconds at which the log file should close after the last log entry.

• wrapper.ping.timeout (1.0.0)

  Configures the number of seconds to allow between two ping responses coming from the JVM.

• wrapper.startup_thread.timeout (3.5.11)

  Configures the number of seconds to allow asynchronous startup operations to be completed.

• wrapper.startup.timeout (1.0.0)

  Configures the number of seconds to allow between the time the Wrapper launches the JVM and the time the JVM responds that the application has started.

• 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.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.jvm_cleanup.timeout (3.4.0)

  Configures the number of seconds allowed for the Wrapper to clean up child processes after the JVM has been shutdown.

• wrapper.jvm_terminate.timeout (3.5.18)

  Configures the number of seconds to allow from the time that the Wrapper asks the system to forcibly terminate the JVM until it confirms that the process actually stopped.

• wrapper.event.<event_name>.command.block.timeout (3.3.0) ( Pro )

  Configures how long the Wrapper will wait for a configured event to complete.

• wrapper.event.<event_name>.email.receive.timeout (3.3.2) ( Pro )
• wrapper.event.<event_name>.email.send.timeout (3.3.2) ( Pro )

• 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.