JDK-7166894 : Add gc cause to GC logging for all collectors
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs24
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2012-05-07
- Updated: 2017-02-11
- Resolved: 2012-05-23
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | Other |
|---|---|---|
7u40Fixed  |
8Fixed |
hs24Fixed |
Related Reports
|
Relates :
|
Description
As part of 7163848 the gc cause was added to all PrintGC logging for G1. It was suggested to do the same for the other collectors. We do risk invalidating parsers with a change like this, but for the Full GC logging there was already "(System)" added to the logging when we did a System.gc(). So it seems lower risk to only add the gc cause to Full GC than to all GCs. Suggested release note: The log output when using -XX:+PrintGC will now list the GC cause in brackets if the flag -XX:+PrintGCCause is set. This flag is off by default in JDK7 and on by default in JDK8. Full GCs triggered by a call to System.gc() used to log "(System.gc)" or "(System)" when -XX:+PrintGC was on. Now this will only be included if -XX:+PrintGCCause is also on.
Comments
|