Re: FAQ, 4.1 OutOfMemoryException

[Andrew Haley]

Chris Burdess writes:
 > Andrew Haley wrote:
 > > Indeed.  The problem is that anything you do when catching an
 > > OutOfMemoryException risks running out of memory!  There's not much
 > > any java program can do other than logging the failure and exiting.
 > 
 > To be pedantic, it's OutOfMemoryError,

Ahh, cut 'n paste.

 > and the same applies largely to any other Error (except possibly in
 > the case of reflection tools).

Not really.  For example, it's not unreasonable to catch
java.lang.NoClassDefFoundError, which may be thrown when a subsystem
is badly configured.

Andrew.