Your "old" is full. Either a memory leak or you simply need more (and old gen of 128Mb is virtually nothing). Increase :-)
regards Leon On Tue, Feb 15, 2011 at 11:43 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > All, > > This is not Tomcat-related but I figured I'd ask as there are some smart > folks here who might be able to give me some good information. > > As the title suggests, I have suffered an OOME in production with the > message "GC overhead limit exceeded". A quick Google search yielded this > StackOverflow thread: > > http://stackoverflow.com/questions/1393486/what-means-the-error-message-java-lang-outofmemoryerror-gc-overhead-limit-excee > > Evidently, when the GC takes a long time to accomplish nothing, you get > this error. > > This error occurred /once/ at 16:39 EDT and it's 17:39 EDT now and I can > see the following heap information from my still-running process: > > Maximum Memory JVM will use: 190775296 bytes (186304 KiB, 181 MiB) > Memory Not yet Allocated to JVM: 0 bytes (0 KiB, 0 MiB) > Total Memory Allocated to JVM: 190775296 bytes (186304 KiB, 181 MiB) > Free Memory: 21809336 (21298 KiB, 20 MiB) > Memory Used by JVM: 168965960 (165005 KiB, 161 MiB) > > The application appears to be running as expected for now. Is it likely > that this was something acute and that my server is okay? Obviously, > increasing heap space is probably a good idea in general in this > situation as it looks like I simply need more for my user load. > Unfortunately, I haven't been keeping GC or other heap records for a > while... I'll certainly be restarting that process. > > The only heap/GC options I've set are: > > - -Xms192M -Xmx192M > > All else is the default for this JVM, which is: > > java version "1.6.0_23" > Java(TM) SE Runtime Environment (build 1.6.0_23-b05) > Java HotSpot(TM) Server VM (build 19.0-b09, mixed mode) > > FYI jmap reports: > > Server compiler detected. > JVM version is 19.0-b09 > > using thread-local object allocation. > Parallel GC with 4 thread(s) > > Heap Configuration: > MinHeapFreeRatio = 40 > MaxHeapFreeRatio = 70 > MaxHeapSize = 201326592 (192.0MB) > NewSize = 1048576 (1.0MB) > MaxNewSize = 4294901760 (4095.9375MB) > OldSize = 4194304 (4.0MB) > NewRatio = 2 > SurvivorRatio = 8 > PermSize = 16777216 (16.0MB) > MaxPermSize = 67108864 (64.0MB) > > Heap Usage: > PS Young Generation > Eden Space: > capacity = 45613056 (43.5MB) > used = 15735344 (15.006393432617188MB) > free = 29877712 (28.493606567382812MB) > 34.49745616693606% used > - From Space: > capacity = 10551296 (10.0625MB) > used = 2172200 (2.0715713500976562MB) > free = 8379096 (7.990928649902344MB) > 20.587044473020185% used > To Space: > capacity = 10158080 (9.6875MB) > used = 0 (0.0MB) > free = 10158080 (9.6875MB) > 0.0% used > PS Old Generation > capacity = 134217728 (128.0MB) > used = 129355080 (123.36261749267578MB) > free = 4862648 (4.637382507324219MB) > 96.37704491615295% used > PS Perm Generation > capacity = 20316160 (19.375MB) > used = 20088520 (19.15790557861328MB) > free = 227640 (0.21709442138671875MB) > 98.87951266381049% used > > Any thoughts? > > Thanks, > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1bAYEACgkQ9CaO5/Lv0PA9dwCfdmJta/0xqhoHOgFaRlezGl7p > 52YAn0QYEK348ZydsLD8TBMpSTnJU/IG > =AbM9 > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
