JDK-8185262 : Keep default logging for Metaspace OOM short and concise
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-07-25
- Updated: 2017-08-25
- Resolved: 2017-07-26
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 10 |
|---|
10 b21Fixed  |
Related Reports
|
Relates :
|
Description
Currently, for info log level (default if -Xlog is given), we dump out the whole classloader data - which prints out all chunks in use, which may be very extensive. It would be better to restrict this very verbose printout to debug (or trace) level and keep the info level printout short and concise.