Bhanu Prasad - 2013-06-02

Hi,

I frequently notice the extending timeout errors and at the same time the users experience slowness in the application requests and the response times are high. Sometimes(when the wrapper process do not receive CPU time for more than CPU timeout threshold value 60 sec) then a restart of service is triggered and all the users thrown out of the application. It is seriously affecting response time measurements and user satisfaction. Request anyone's help in this regard.

Would like to know the factor causing this timeout and how it can be solved.
FYI, when we check CPU usage, it is under normal range.

INFO | wrapper | 2013/05/23 03:31:01 | Wrapper Process has not received any CPU time for 21 seconds. Extending timeouts.
DEBUG | wrapperp | 2013/05/23 03:31:01 | send a packet PING : ping
INFO | jvm 2 | 2013/05/23 03:31:01 | WrapperManager Debug: Received a packet PING : ping
INFO | jvm 2 | 2013/05/23 03:31:01 | WrapperManager Debug: Send a packet PING : ping
DEBUG | wrapperp | 2013/05/23 03:31:01 | read a packet PING : ping
INFO | wrapper | 2013/05/23 03:31:16 | Wrapper Process has not received any CPU time for 13 seconds. Extending timeouts.
DEBUG | wrapperp | 2013/05/23 03:31:23 | send a packet PING : ping
INFO | jvm 2 | 2013/05/23 03:31:23 | WrapperManager Debug: Received a packet PING : ping
INFO | jvm 2 | 2013/05/23 03:31:23 | WrapperManager Debug: Send a packet PING : ping
DEBUG | wrapperp | 2013/05/23 03:31:23 | read a packet PING : ping
INFO | jvm 2 | 2013/05/23 03:32:52 | WrapperManager Debug: Read Timed out. (Last Ping was 55400 milliseconds ago)
INFO | wrapper | 2013/05/23 03:32:52 | Wrapper Process has not received any CPU time for 79 seconds. Extending timeouts.