Fixing the bug would be cool, but the "bug" is actually just too many users contending for the same heap space, so that's going to be tough. I'd thought of the log watcher, but that seems a rather blunt instrument; I was thinking there might be some kind of Tomcat (or JVM) intrinsic mechanism for this.
-----Original Message----- From: Leon Rosenberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 9:46 AM To: Tomcat Users List Subject: Re: Recovery from OutOfMemoryError? variant 1: a log watcher that checks for OOMe and restarts tomcat variant 2: fix the bug :-) regards Leon On 7/31/07, Craig Berry <[EMAIL PROTECTED]> wrote: > Our Tomcat-based app suffers from occasional OutOfMemoryErrors. We have > found that we need to manually restart Tomcat when these happen; > frequently the Tomcat process appears to be working after the error, but > is actually crippled in one way or another by the loss of some key > thread. > > > > We would very much like to trigger an automated Tomcat restart when an > OOME occurs. Does anyone have suggestions on the cleanest, safest way > to arrange this? (We're running Tomcat as a normal process under Linux, > if that matters.) > > > > -- > > Craig Berry > Principal Architect and Technical Manager > > PortBlue Corporation (http://www.portblue.com/) > > > > > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
