Menu
▾
▴
Re: [Wrapper-user] mass ping time-out event
|
From: matt p. <pie...@ho...> - 2008-08-04 15:40:45
|
Here is the wrapper log from one of the instances (all 8 have the same signature, and all send the last ping between 16:40:23 and 16:40:25): INFO | jvm 1 | 2008/08/01 16:40:01 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:01 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:05 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:05 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:09 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:09 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:13 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:13 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:17 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:17 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:21 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:21 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:40:25 | Received a packet PING : pingINFO | jvm 1 | 2008/08/01 16:40:25 | Send a packet PING : okINFO | jvm 1 | 2008/08/01 16:45:25 | Read Timed out. (Last Ping was 300000 milliseconds ago)INFO | jvm 1 | 2008/08/01 16:50:25 | Read Timed out. (Last Ping was 600000 milliseconds ago)INFO | jvm 1 | 2008/08/01 16:50:25 | Wrapper Manager: JVM did not exit. Give up.INFO | jvm 1 | 2008/08/01 16:50:25 | Wrapper Manager: ShutdownHook startedINFO | jvm 1 | 2008/08/01 16:50:25 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-HookINFO | jvm 1 | 2008/08/01 16:50:25 | Send a packet STOP : 0INFO | jvm 1 | 2008/08/01 16:50:26 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process.INFO | jvm 1 | 2008/08/01 16:50:26 | calling listener.stop()INFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: stop(0)INFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: invoking stop main methodINFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: stop main method completedINFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: start main method completedINFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: stopping. Waiting for 2 threads to complete.INFO | jvm 1 | 2008/08/01 16:50:27 | WrapperStartStopApp: stopping. Waiting for 1 threads to complete.INFO | jvm 1 | 2008/08/01 16:50:28 | WrapperStartStopApp: stopping. Waiting for 1 threads to complete.INFO | jvm 1 | 2008/08/01 16:50:29 | WrapperStartStopApp: stopping. Waiting for 1 threads to complete.INFO | jvm 1 | 2008/08/01 16:50:30 | WrapperStartStopApp: stopping. Waiting for 1 threads to complete. From: pie...@ho...: wra...@li...: Mon, 4 Aug 2008 11:15:30 -0400Subject: [Wrapper-user] mass ping time-out event My company uses version 3.1.1 of the wrapper to run 6 different production applications spread over 4 Redhat Linux servers. We have a similar setup in our QA environment. All of our production applications run far under capacity. We never come near to utilizing all the memory allocated to the VM, and there is plenty free on the box. The same goes for CPU. We have various timeout configurations among them--the 4 webapps are tomcats with a 10 minute timeout.We had an event last week in which all of our wrappers simultaneously timed out. Within a 2 second period, 8 different wrappers on 6 different servers running 3 distinct applications on 2 different subnets sent one last ping to their respective VMs, and that was the last line of logging we saw from any of the wrappers until their shutdowns (with the exception of the half-way to time-out warning).Does anyone have an idea about what sort of event could cause this? Reveal your inner athlete and share it with friends on Windows Live. Share now! _________________________________________________________________ Get more from your digital life. Find out how. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008 |
