-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFym3I9CaO5/Lv0PARAo5MAJ9pBpTS+bi8FIl0UPm/I3IJAxi1WQCdFAWN PbonyKzrLbbTfztMBXyxX1A= =IkDu -----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]
