Analyzing the Oracle Apps 11i JVM logs

on Sunday 20 May 2012

Analyzing the Oracle Apps 11i JVM logs

 In order to analyze Oracle apps 11i JVM, lets open stdout file for one of Group, I have selected OACoreGroup here,  log file ($IAS_ORACLE_HOME/Apache/Jserv/logs/jvm), open file like OACoreGroup.X.stdout you should see output like below if GC(Grabage Collector) is set in Verbose mode.

48561.624: [GC 325980K->170382K(519168K), 0.2751056 secs]
49307.880: [GC 334862K->179171K(519168K), 0.2660486 secs]
50236.662: [GC 343651K->187797K(519168K), 0.2518720 secs]
50515.494: [Full GC[Unloading class sun. reflect. Generated Method Accessor 143]
[Unloading class sun. reflect. GeneratedMethodAccessor136]
[Unloading class sun. reflect. GeneratedMethodAccessor74]

Here first entry is time since JVM was started so each time you bounce Apache it will be reset to 0. So difference between two entries is seconds after which GC (Garbage Collector) was executed. First entry in bracket [ is Heap Size at start of GC & Second entry is Heap Size after GC was executed. Number mentioned in round bracket () is heap size currently attocated in K. If you see GC running very frequently , you can start thinking of increasing JVM heap size
First three entries were for Minor Garbage Collector & fourth one is FULL GC is for Full Garbage Collector.

0 comments:

Post a Comment