The Wrapper uses a ping system as one of its methods of monitoring the JVM.
The Wrapper will send a ping to the JVM and then wait for a ping response.
If a response has not been received for more than the time configured in wrapper.ping.timeout property,
then the Wrapper will decide that the JVM is frozen and forcibly kill and restart it.
The ping system is fairly reliable, but in some cases when there is heavy disk swapping or another process is hogging resources,
the Wrapper can potentially decide that the JVM is frozen when it is simply stuck temporarily.
Obviously this is a bad thing as regardless of the cause, the JVM is not in a state where it can reply to requests.
But it may be preferable to wait a bit longer rather than restarting the JVM in this case.
If you simply extend the length of the wrapper.ping.timeout property to a large value,
false restarts will become much less likely, but at the same time, the Wrapper will also become much less responsive to actual freezes.
But you have no idea how common the slow ping responses are or how much extra leeway you have given yourself.
This property allows you specify that the Wrapper should log a warning whenever a ping response of JVM takes longer than a threshold number of seconds.
Setting this property value to "0" (zero) means never log any warnings.
Log Example of slow ping responses during heavy swapping:
wrapper | Pinging the JVM took 4 seconds to respond.
wrapper | Pinging the JVM took 9 seconds to respond.
wrapper | Pinging the JVM took 10 seconds to respond.
wrapper | Pinging the JVM took 6 seconds to respond.
wrapper | Pinging the JVM took 2 seconds to respond.
This property allows you specify at which log level the ping alert messages will be logged in the log file.