Compatibility :	3.4.0
Editions :
Platforms :

Maximum number of seconds allowed for the Wrapper to clean up after the JVM has been completely shutdown and before starting the process to either start a new JVM or shutdown the Wrapper. Setting this property value to "0" (zero) means never time out.

The default value is "10 seconds".

wrapper.jvm_cleanup.timeout=10

The cleanup process consists of shutting down all managed child processes which were launched using the WrapperManager.exec() methods without setting the detached flag.

The Wrapper will attempt to shutdown any child processes still running after the JVM has exited cleanly. On UNIX platforms, this is done by sending a SIGTERM to each process and then waiting for them to exit. On Windows platforms, a WM_CLOSE message will be sent to each window owned by the child process. Many Windows applications may display save dialogs when they are asked to shutdown and thus may not completely exit on their own. It is currently not possible to send a CTRL-C to Windows console processes to ask them to shutdown cleanly, so they are currently terminated immediately.

If all child processes are determined to have been shutdown, then the Wrapper will continue before the timeout expires.

Once the timeout expires, the Wrapper will forcibly close any child processes still running. On UNIX platforms, this is done by sending a SIGKILL to each process. On Windows, the process is forcibly terminated.

Information about child processes will only be logged when DEBUG output is enabled, or when the wrapper.child.status.loglevel property is set to a level which will be visible.

Case Example:

The following example shows an example of 3 child processes being shutdown cleanly. 2 shutdown immediately, and the 3rd takes a few seconds.

wrapper  | Requesting shutdown of managed child process. PID: 1852
wrapper  | Requesting shutdown of managed child process. PID: 3584
wrapper  | Requesting shutdown of managed child process. PID: 3944
wrapper  | 3 managed child processes still running.
wrapper  | Managed child process confirmed shutdown. PID: 1852
wrapper  | Managed child process confirmed shutdown. PID: 3584
wrapper  | 1 managed child processes still running.
wrapper  | 1 managed child processes still running.
wrapper  | Managed child process confirmed shutdown. PID: 3944
wrapper  | All managed child processes shutdown.
wrapper  | <-- Wrapper Stopped

The following example shows an example of 2 child processes being shutdown cleanly, and a 3rd that times out and is killed.

wrapper  | Requesting shutdown of managed child process. PID: 3276
wrapper  | Requesting shutdown of managed child process. PID: 3328
wrapper  | Requesting shutdown of managed child process. PID: 1200
wrapper  | 3 managed child processes still running.
wrapper  | Managed child process confirmed shutdown. PID: 3276
wrapper  | Managed child process confirmed shutdown. PID: 3328
wrapper  | 1 managed child processes still running.
wrapper  | 1 managed child processes still running.
wrapper  | 1 managed child processes still running.
wrapper  | 1 managed child processes still running.
wrapper  | Forcing termination of managed child process. PID: 1200
wrapper  | Managed child process confirmed shutdown. PID: 1200
wrapper  | All managed child processes shutdown.
wrapper  | <-- Wrapper Stopped

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