wrapper.shutdown.timeout
Compatibility :2.2.7
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/Linux

WARNING

DO NOT modify any of these parameters unless you have read this property description. Incorrect settings can cause the Wrapper to fail to operate as expected.

Number of seconds to allow between the time that the Wrapper asks the JVM to shutdown and the time that the JVM side of the Wrapper responds that it is stopping. Setting this property value to "0" (zero) means never time out.

The default value is "30 seconds".

Example: 
wrapper.shutdown.timeout=30

Problems? :

If you are experiencing timeout problems as your application is shutting down, you may want to consider extending this timeout. This can happen in cases where the shutdown code within the application takes a long time to complete. As a test, try setting this property value to something like 300 (5 minutes) and see if this makes the problem go away.

If the application still times out quicker than the 5 minute test timeout, then the problem may be in a later phase of shutdown. Take a look at the wrapper.jvm_exit.timeout property.

If the application still times out after waiting the full 5 minutes, then you will have to do some debugging of your application to see what is taking so long. If it is possible to speed up the application's shutdown phase, that would be best. Otherwise set the timeout to a value that allows the application to shutdown cleanly.

It is best to choose a value which is long enough to let the application run reliably, but short enough that the Wrapper will react as quickly as possible in the event of an actual JVM hang.

WrapperManager.signalStopping(n):

If the shutdown procedure sometimes takes a long time, one alternative to setting a long timeout is to periodically call the WrapperManager.signalStopping(n) method. This method lets the Wrapper know that the JVM is alive and the application's shutdown is going well. The report will be repeated as many times as needed. Therefore, that additional time is required, and it may take much longer time on the shutdown.

If you are having problems with your application timing out on shutdown, it may be useful to have the Wrapper attempt to request a thread dump prior to killing the JVM. This will usually make it clear what was preventing the JVM from shutting down. Please see the wrapper.request_thread_dump_on_failed_jvm_exit property for more information.

WARNING

While the ability is there, be aware that setting this property value to "0" (zero) (= disable Timeout) or some large value will mean that the Wrapper's ability to detect a JVM hang during the shutdown phase will be disabled.

WARNING

While the wrapper.java.detect_debug_jvm property is set to "TRUE" and the Debugger Detection is functioning, this "timeout" property will be ignored.

Reference: Timeout
  • 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.

Reference: Shutdown

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.