Menu
▾
▴
Re: [Wrapper-user] mass ping time-out event
|
From: Leif M. <le...@ta...> - 2008-08-04 19:47:27
|
Matt, There was an overflow bug with the timer fixed in version 3.1.2 which caused the wrapper incorrectly timeout at regular fixed intervals. Most likely this is the problem that you have encountered. Please see the release notes for the 3.1.2 release: http://wrapper.tanukisoftware.org/doc/english/release-notes.html#3.1.2 Here is the bug: http://sourceforge.net/tracker/?func=detail&aid=1014405&group_id=39428&atid=425187 There have been a number of bugs fixed and new features implemented so we always recommend using the latest version. If the new licensing is an issue, 3.2.3 was pretty stable. If you need to continue using 3.1.1, try setting the wrapper.use_system_time=FALSE property, it will use the new timer which does not have the above bug. This new timer is also much more resilient under heavy loads and is the default as of 3.2.0 http://wrapper.tanukisoftware.org/doc/english/prop-use-system-time.html Let me know how this works for you. Cheers, Leif On Mon, Aug 4, 2008 at 8:40 AM, matt pierce <pie...@ho...> wrote: > 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 : ping > INFO | jvm 1 | 2008/08/01 16:40:01 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:05 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:05 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:09 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:09 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:13 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:13 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:17 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:17 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:21 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:21 | Send a packet PING : ok > INFO | jvm 1 | 2008/08/01 16:40:25 | Received a packet PING : ping > INFO | jvm 1 | 2008/08/01 16:40:25 | Send a packet PING : ok > INFO | 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 > started > INFO | jvm 1 | 2008/08/01 16:50:25 | WrapperManager.stop(0) called by > thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/08/01 16:50:25 | Send a packet STOP : 0 > INFO | 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 method > INFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: stop main > method completed > INFO | jvm 1 | 2008/08/01 16:50:26 | WrapperStartStopApp: start main > method completed > INFO | 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... > To: wra...@li... > Date: Mon, 4 Aug 2008 11:15:30 -0400 > Subject: [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. > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
