Skip to content
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

Closed
ghost opened this issue Jul 19, 2014 · 7 comments
Closed

Parsing error OpenJDK1.8.0 #105

ghost opened this issue Jul 19, 2014 · 7 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Jul 19, 2014

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

@chewiebug
Copy link
Owner

Hi Jayneel,

Hmm, GCViewer should be able to parse the reasons in the latest version.
Could you please make sure, that you download
https://github.com/chewiebug/GCViewer/wiki/Changelog the latest
version (even if you alread have 1.34-SNAPSHOT - there are many
1.34-SNAPSHOT versions)?

Please tell me, what a fresh download of GCViewer does with your log file.

Best regards,
Jörg

@ghost
Copy link
Author

ghost commented Jul 21, 2014

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,
Jayneel

@chewiebug
Copy link
Owner

Hi Jayneel,

Thanks for checking! Could you please send me a sample of the log that can't be parsed?

Best regards,
Jörg

-------- Ursprüngliche Nachricht --------
Von: jayneelgandhi notifications@github.com
Gesendet: 21. Juli 2014 20:47:08 MESZ
An: chewiebug/GCViewer GCViewer@noreply.github.com
CC: chewiebug gcviewer@gmx.ch
Betreff: Re: [GCViewer] Parsing error OpenJDK1.8.0 (#105)

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,
Jayneel


Reply to this email directly or view it on GitHub:
#105 (comment)

@ghost
Copy link
Author

ghost commented Jul 21, 2014

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,
Jayneel

@chewiebug
Copy link
Owner

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 -XX:+PrintTenuringDistribution. Now they should be.

Does the latest version of GCViewer now parse your log?

Best regards,
Jörg

@ghost
Copy link
Author

ghost commented Jul 22, 2014

Hi Jörg,

Thanks for fixing this problem so quickly. It works nicely now.

Regards,
Jayneel

@chewiebug
Copy link
Owner

Hi Jayneel,

Thank you very much for reporting and testing this bug!

Best regards,
Jörg

@chewiebug chewiebug added the bug label Jul 22, 2014
@chewiebug chewiebug added this to the 1.34 milestone Jul 22, 2014
@chewiebug chewiebug self-assigned this Jul 22, 2014
chewiebug added a commit that referenced this issue Aug 2, 2014
- 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.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant