wrapper.ping.alert.<x> Properties Overview |
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. 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. |
wrapper.ping.alert.threshold |
||||||||||
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. Starting with Wrapper version 3.5.21, the professional edition of the Wrapper will also fire a jvm_ping_slow event as soon as the threshold is exceeded, and a jvm_ping_response_slow event when the ping response has finally been received. The default value is 1/4 the length of the ping timeout in seconds. Setting this property value to "0" (zero) means never log any warnings.
|
wrapper.ping.alert.loglevel |
||||||||
This property allows you specify at which log level the ping alert messages will be logged in the log file. The default value is "STATUS". The possible values are exactly the same as the console output loglevel, the log file output loglevel, etc.
|
Reference: ping |
|
Reference: Loglevel |
|