Skip to main content

alphaWorks  >  Forums  >  Pattern Modeling and Analysis Tool for IBM Java Garbage Collector  >  developerWorks

Parsing error when processing verbosegc logs from Sun HotSpot JVM 1.6    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
Permlink Replies: 0 - Pages: 1 Threads: [ Previous | Next ]
aputilin

Posts: 3
Registered: Sep 21, 2005 10:28:24 AM
Parsing error when processing verbosegc logs from Sun HotSpot JVM 1.6
Posted: Mar 16, 2009 01:01:22 AM
Click to report abuse...   Click to reply to this thread Reply
Firstly, I would like to say thanks to Jinwoo for the great tools that are used by developers and system admins around the world for analysis and trobleshooting JVM problems.

I am trying to use the PMAT 33 for analysis of verbosegc logs collected from the Sun HotSpot JVM 1.6 on Solaris (java full version "1.6.0_10-b33") and I am getting the following error:

Exception while parsing line 5 : : 104960K->7240K(118016K), 0.0661423 secs] 108697K->10978K(2084096K), 0.0663877 secs] Times: user=0.24 sys=0.09, real=0.07 secs
java.lang.NumberFormatException: For input string: "real=0.07"
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at java.lang.Float.parseFloat(Unknown Source)
at com.ibm.jinwoo.gc.FileTask.processSolaris(FileTask.java:4606)
at com.ibm.jinwoo.gc.FileTask$ActualTask.<init>(FileTask.java:306)
at com.ibm.jinwoo.gc.FileTask$1.construct(FileTask.java:1782)
at com.ibm.jinwoo.gc.ThreadHandler$1.run(ThreadHandler.java:23)
at java.lang.Thread.run(Unknown Source)

A typical log entry from the verbose GC log file is:
11.756: [Full GC (System) 11.756: CMS: 0K->3737K(1966080K), 0.6801851 secs 54605K->3737K(2084096K), CMS Perm : 10523K->10513K(16384K)], 0.6846036 secs Times: user=0.47 sys=0.21, real=0.69 secs
26.430: [GC 26.430: [ParNew
Desired survivor size 6684672 bytes, new threshold 1 (max 4)
  • age 1: 7355152 bytes, 7355152 total
: 104960K->7240K(118016K), 0.0661423 secs] 108697K->10978K(2084096K), 0.0663877 secs] Times: user=0.24 sys=0.09, real=0.07 secs

It looks like the tool can not parse the value starting with "real=". I modified the log file by replacing all occurencies of "real=" with "". This seems to work and the file gets loaded into the tool. However, it is a bit of a pain to do it every time.

Would it be possible to fix this parsing issue.

Many thanks in advance.
Albert Putilin

Point your RSS reader here for a feed of the latest messages in all forums