• Configuration Property Overview
• Property List by Category
• Property List by Name
• Advanced Properties

Compatibility :	1.0.0
Editions :
Platforms :

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 Wrapper pinging the JVM and the response from the JVM.

The default value is "30 seconds".

wrapper.ping.timeout=30

Setting this property value to "0" (zero) means never time out. The ping timeout must be at least 5 seconds longer than the value of wrapper.ping.interval. The Wrapper will modify the value at run time if necessary to avoid problems.

In normal operation, the Wrapper pings the JVM once every 5 seconds to make sure that its process has not frozen up. The ping timeout is the amount of time to allow for a response from the JVM before the Wrapper assumes that it is hung and restarts it.

This property also controls the amount of time that the JVM will allow to pass without being pinged by the Wrapper. If the Wrapper does not ping the JVM for longer than the specified timeout, it will exit allowing the Wrapper to resynch by launching a new JVM. This also makes sure that the JVM will exit if the Wrapper process is terminated abnormally. (By killing the Wrapper process in the Windows Task Manager, or using "kill -9" signal on Unix systems.)

With the addition of the wrapper.cpu.timeout property, there is now almost no reason why you should ever need to change this property. The only reasons why you should be getting ping timeouts are if the system is under heavy load or if the JVM is really hung. The CPU timeout should now detect any problems in with CPU.

WARNING

While the ability is there, be aware that setting this property to "0" (zero) (= disable Timeout) or some large value will mean that the Wrapper's ability to detect a JVM hang as it is running will be disabled. Also note that if the Wrapper process is killed abnormally or God forbid crashes, then the JVM will never attempt to resynch with the Wrapper. If the Wrapper was running as a Windows Service at the time, it may be necessary to then reboot the machine to stop Java process. With normal ping timeouts, the JVM would exit on its own after a few seconds.

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.

• wrapper.ping.interval
• wrapper.ping.interval.logged
• wrapper.ping.timeout

• wrapper.cpu.timeout
• wrapper.ping.timeout
• wrapper.startup.timeout
• wrapper.shutdown.timeout
• wrapper.jvm_exit.timeout
• wrapper.jvm_cleanup.timeout

If you notice something that is incorrect, missing, or simply feel that some part of this page could be explained better, feel free to log in and add a comment. You will need to register before you can log on.