[Wrapper-user] mass ping time-out event

[matt p. <pie...@ho...>]

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.
http://revealyourinnerathlete.windowslive.com?locale=en-us&ocid=TXT_TAGLM_WLYIA_whichathlete_us