JDK-8150865 : SQE test: GC unified logging: check that dynamic log level doesn't break anything
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-02-29
- Updated: 2016-05-26
- Resolved: 2016-05-11
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 9 |
|---|
9 b120Fixed  |
Related Reports
|
Blocks :
|
|
|
Duplicate :
|
Description
New VM logging mechanism introduced in JDK9 allows dynamic change of the logging level, which means that level might change during a VM method execution. There should be a test checking that log level change will never cause a crash. Test idea: An application with several worker threads which allocate/release memory. In addition to those threads the application starts a couple of threads which set a random level of logging. The test start this app with -Xlog:all for several seconds, expecting for no crash.