Getting Started with vFabric Hyperic v.5.7 - VMware

Java Service Wrapper TimeoutUnder high load, the agent may become unresponsive. If this occurs and there are nocoincident errors or warnings in the agent log that indicate another explanation, it may be thatthe agent JVM was starved for memory, and unresponsive to a ping from the Java ServiceWrapper (JSW).In that case the wrapper.log file will contain an entry like this:ERROR | wrapper | 2009/01/15 02:15:18 | JVM appears hung: Timedout waiting for signal from JVM.To resolve the problem, you can configure the JSW to give the agent more time to respond tostartup and ping requests.Increase the JSW's timeout period from 30 seconds to 300. To do so, add this property toAGENT_HOME/bundles/agent-4.x.xxxx/conf/wrapper.conf.wrapper.ping.timeout=300This will cause the JSW to wait longer for a ping response before determining that the JVM ishung.Increase the agent's startup timeout from 30 seconds to 300. This will give the agent more timeto start up before wrapper gives up on it and kills the process. To do so, add this property value:wrapper.startup.timeout=300toAgentHome/bundles/agent-4.x.xxxx/conf/wrapper.conf110