Re: Out-of-Memory Handling in Long-Running / Server Applications
Jeff Kesselman <[email protected]> Sun, 13 Apr 2008 20:26:20 -0400
| Newsgroups | gmane.comp.windows.devel.java.advanced |
|---|---|
| Message-ID | <[email protected]> |
Endre Stølsvik wrote: > Peter Booth wrote: >> Here's my two cents: >> >> Catching an OutOfMemory error is a waste of time, because by the tim >> eyou get that error all bets ar eoff an dthere is no guarantee that the >> VM is functional. > > As mentioned, I've also heard this. I'd like to have pointers to actual > documentation describing this, Some information: http://java.sun.com/docs/books/performance/1st_edition/html/JPAppGC.fm.html#998394 Some more information: http://java.sun.com/j2se/1.5.0/docs/api/ In particular: "Thrown when the Java Virtual Machine cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector." =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com