-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
On 4/22/2009 12:16 PM, Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:ch...@christopherschultz.net] >> Subject: Re: Headstart on "Resolving OOM-PermGen errors on webapp >> reload" >> >> It's also a shame that the values for -Xmx aren't shown > > It is - it's the MaxHeapSize under Heap Configuration. > > The odd thing in your report is MaxNewSize, which is clearly out of > whack; not sure at this point where that comes from. I'm using: java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode) and the heap configuration, again, for reference is: Heap Configuration: MinHeapFreeRatio = 40 MaxHeapFreeRatio = 70 MaxHeapSize = 67108864 (64.0MB) NewSize = 655360 (0.625MB) MaxNewSize = 4294901760 (4095.9375MB) OldSize = 1441792 (1.375MB) NewRatio = 12 SurvivorRatio = 8 PermSize = 8388608 (8.0MB) MaxPermSize = 67108864 (64.0MB) Does that mean that, technically speaking, PermGen is allowed to grow to take over the whole heap? Clearly, that isn't technically possible (because the other heap sections will be non-zero) but it seems weird that the max permgen is the same as the max heap. I wonder if MaxNewSize is set to be the process max memory (4GB... or just shy of that). That would be a *very* big NewSize. Odd that the NewSize can exceed the maximum heap. You *did* say it was unnecessarily complicated ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknva54ACgkQ9CaO5/Lv0PCwOwCglqyVZQVgBpbDMuKtTo77aQ7T mNYAn2yb4DO7tq1pQuJ+a/iB4myz66fL =hLg9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
