-
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
Do not flag "application stopped/concurrent time" lines as parsing errors #90
Comments
Hi Sergei, Thank you for testing this! I'll first filter those lines out so as to Best regards, |
…`-XX:+PrintGCApplicationStoppedTime` and show in chart / statistics) addresses issues - #106 G1; combination of -XX:+PrintGCApplicationStoppedTime, -XX:+PrintTenuringDistribution, -XX:+PrintAdaptiveSizePolicy - #91 G1; combination of -XX:+PrintGCApplicationStoppedTime, -XX:+PrintTenuringDistribution - #90 (Oracle Parser without G1); -XX:+PrintGCApplicationStoppedTime - #25 G1 and others; evaluate -XX:+PrintGCApplicationStoppedTime
Hi Sergei, With my merge, this issues should also be addressed. Does it now work for you? Best regards, |
Assuming that it works, I close this issue. If it shoulnd't please reopen it. Best regards, |
I ran my application with the following JVM options:
When I tried to load the result into the GCViewer, it produced a lot of warning messages like those:
The GC output is as follows:
It looks like starting with Java7, JVM started to prepend timestamps to all "application stopped/concurrent time" lines. Java8 behaves in a similar way.
At best these log lines should be ignored by GCviewer, but ideally it would be great if it parsed and analysed them. It is not uncommon that the application is stopped for non-GC reason, and it would be great to have some statistics (with charts!) on stop/concurrent times, their distribution and any outliers.
The text was updated successfully, but these errors were encountered: