On 7/31/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > > Subject: Re: Recovery from OutOfMemoryError? > > > > A thread that suffers an OOME is pretty much hosed, anyway, so > > counting on it to do any kind of recovery is difficult. > > Why do you say that? The only thing that failed is the allocation of > some particular object, leaving the rest of the thread's state intact. > In most cases, it's easy to return a failure notification to the caller > of whatever method encountered the error. Unless one's design is based > on wishful thinking, of course...
Thats however strongly depend on where it happened... if for example the code in question was a middleware stub which is left in unpredictable state, or the orb itself, or any kind of stack somewhere, or a processing queue, or some background threads... or 3rd party libraries... chances to recover from an oome are pretty low in my opinion, and even if you recover (unless it was an unusually expensive request) the next request you get will bring you into same situation... I think there are very few places where an oome should be caught and can be handled properly, or you have to surround each new with try/catch.... regards Leon > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > --------------------------------------------------------------------- > 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]
