tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: OutOfMemoryError (but not really out of memory?) cause tomcatprocesses to hang
Date Thu, 08 Feb 2007 00:24:40 GMT
Hash: SHA1


Caldarale, Charles R wrote:
>> In fact, this is often when OOMs occur, since the JVM is trying
>> hard to avoid the OOM in the first place.
> Uhhh - no.  The JVM will not return an OOME until the GC is completely
> finished and the request still cannot be satisfied

The collector itself requires the creation of Java objects on the heap.
If the collector does not have enough memory to do the collection, it
can easily barf.

>> After an OOM is thrown, the JVM is basically completely hosed.
> Definitely not true.  The JVM is still functional, although the app
> (Tomcat, in this case) may not be able to proceed.

Fair enough. But if Tomcat isn't happy, nobody's happy ;)

> However, the 64m given to the PermGen is rather small for an app
> server

It's clear from the OP's heap stats that the Perm space is busting. Odd,
though: the MaxPermSpace is 64MB, but she is topping out at 20MB or so.

- -chris
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla -


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message