-
Notifications
You must be signed in to change notification settings - Fork 978
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Parsing error OpenJDK1.8.0 #105
Comments
Hi Jayneel, Hmm, GCViewer should be able to parse the reasons in the latest version. Please tell me, what a fresh download of GCViewer does with your log file. Best regards, |
Hi Jörg, I downloaded the snapshot today and tried it again. Gcviewer cannot handle it. I had to remove the reasons for GC pause to make it work. Regards, |
Hi Jayneel, Thanks for checking! Could you please send me a sample of the log that can't be parsed? Best regards, -------- Ursprüngliche Nachricht -------- Hi Jörg, I downloaded the snapshot today and tried it again. Gcviewer cannot handle it. I had to remove the reasons for GC pause to make it work. Regards, Reply to this email directly or view it on GitHub: |
Hi Jörg, I have uploaded a part of the log file here: http://pages.cs.wisc.edu/~jayneel/error.log This should recreate the problem. There are a lot different reasons why a young generation or mixed generation pauses occur. The log file only gives one of the reasons. I had cut it down due the size of the log file. If you remove from the log file I provided, "(G1 Evacuation Pause)", then it parses fine. Regards, |
Hi Jayneel, Thanks for the sample log. I have been able to reproduce the problem and provide a fix. Reasons in GC events were already supported before, but not in conjunction with Does the latest version of GCViewer now parse your log? Best regards, |
Hi Jörg, Thanks for fixing this problem so quickly. It works nicely now. Regards, |
Hi Jayneel, Thank you very much for reporting and testing this bug! Best regards, |
- fix log entries, where gc cause is printed along with PrintTenuringDistribution (#105) - Adding the ability to specify the type of output to a file while maintaining backwards compatibility with the current options. Also allowing a new output type CSV_TS which prefers the unix timestamp of the entry first.
Hi Chewiebug,
I got his parsing error (using 1.34-SNAPSHOT) on OpenJDK 1.8.:
Jul 18, 2014 6:41:48 PM com.tagtraum.perf.gcviewer.imp.DataReaderSun1_6_0G1 read
WARNING: com.tagtraum.perf.gcviewer.imp.ParseException: java.lang.ArrayIndexOutOfBoundsException: 49 Line 7038: 1609.236: [GC pause (G1 Evacuation Pause) (young)
Jul 18, 2014 6:41:48 PM com.tagtraum.perf.gcviewer.imp.DataReaderSun1_6_0G1 read
WARNING: com.tagtraum.perf.gcviewer.imp.UnknownGcTypeException: Unknown gc type: '' Line 7055: , 0.5996270 secs]
The problem is that new logging default options have a reason associated with each GC pause, in this case (G1 Evacuation Pause). The parser is not able ignore these reasons.
839.770: [GC pause (G1 Evacuation Pause) (young)
Removing the reason, fixes the problem.
Thanks,
Jayneel
The text was updated successfully, but these errors were encountered: