-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

Caldarale, Charles R wrote:
>> From: Leon Rosenberg [mailto:[EMAIL PROTECTED] 
>> Subject: Re: Recovery from OutOfMemoryError?
>>
>> 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...
> 
> Agreed - but the above defines software of somewhat questionable
> quality, not written with robustness in mind.  But if it's not a
> critical environment, the occasional outage may not matter, so robust
> algorithms are not always needed.

Are you suggesting that all methods should be written as a loops around
attempts to do real work, catching OOME and re-trying until the work
gets done? That's what it sounds like, here.

IMHO, it's not a library's problem if there wasn't enough memory to
perform its duty. It's the driver's responsibility to catch and
re-attempt anything important.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGr7gq9CaO5/Lv0PARAjYhAJ0eyYzCaDls9rsjrvoJS6xu6XogCgCeKgr+
acntG1IntJLIABNbcEFKOh0=
=thpd
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to